What is Silvertail Syslog syntax
Originally Published: 2013-06-24
Article Number
Issue
Resolution
We rely on the syslog facility to write the logs so the message are consistent to syslog.
The format is as follows.
Date Time hostname source(sts_component_name)[PID]:[severity level keyword] {component instance #} {component instance #-dup} message
IE: Nov 1 01:01:15 silvertswddprc mitigator[8540]:[crit] 0 0 message
The numbers between severity level keyword and message represent the instanceID of the component.
Some components can have multiple instances running on the same server.
In such cases, the instanceID would tell the difference.
The PID would be different as well but the Instance would tie it back to the service name which also ends with the instanceID
Related Articles
How to send Operating System logs in /var/log/messages file to a remote syslog server in RSA Authentication Manager 8.6 o… 247Number of Views How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog 1.78KNumber of Views How to verify RSA Authentication Manager (AM) 8.1 is sending syslog data to a remote syslog server. 1.27KNumber of Views Understanding RSA Authentication Manager logging fields when they are forwarded to syslog 610Number of Views Active Directory AFX test connector capability fails with 'Invalid DN Syntax' and 'Error processing name' errors in RSA Id… 114Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0 Patch 09 Release Notes RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?