Understanding logging in Matrix
Logging captures events that occur in the application and between assets. These events may range from informational to critical.
Logging creates an audit trail, or transaction log, allowing you as an administrator to see who did what and when they did it. You may need this information for compliance or other reasons.
Another reason logging can be useful is if you have a problem with the application, the log events will help identify where the issue is occurring.
How to view event logs
Event logs are useful for troubleshooting, compliance, and more. View the event logs at any time.
To view event logs:
1. From the main toolbar, choose System > System Logs.
2. Type in the Search box to show log events containing your text.
Example: For example, type Info to show informational events only.
 
The events logs are now showing.
 
How to send Syslog messages
Syslog is widely used for message logging and separates the application generating the messages from the program that reports and analyzes them. Matrix can send messages to your Syslog server.
To send log events and alarm notifications, first configure your server and recipient settings.
Configure your server settings:
1. From the main toolbar, choose System > System Logs > Remote Settings.
2. Select Syslog Enabled.
3. Configure the options.
For details, use the information in Syslog settings.
4. Click OK.
 
Matrix will send logged events to your Syslog server.
 
Syslog settings
 
Syslog Enabled
If selected, system logs are forwarded to a Syslog server.
System logs remain accessible through the dashboard and CLI interfaces.
Syslog Server
The host address of the Syslog server.
Include up to 10 Syslog servers by separating each with a comma ','.
Syslog Port
The port number of the Syslog server.
If more than one Syslog server is specified, this port is used for each.
Syslog Severity
The minimum severity level of log events sent to the Syslog server.
 
Informational: Contains normal operational messages. No action is required.
Warning: Contains cautionary messages. No error has occurred but an error may occur if no corrective action is taken.
Critical: Contains fault-finding messages. Corrective action should be taken promptly.
 
Log events of lower severity are not sent.
 
How to send SNMP traps
Events recorded in the Matrix log can be sent as SNMP traps. Doing so allows you to monitor Matrix activity and trigger automated processes to start when certain events occur.
SNMP traps are widely used for sending notifications from one application to another, generally for alerting or notification purposes.
To send log events and alarm notifications, first configure your server and recipient settings.
Configure your server settings:
1. From the main toolbar, choose System > System Logs > Remote Settings.
2. Select SNMP Enabled.
3. Configure the options.
For details, use the information in SNMP trap settings.
4. Click OK.
 
Matrix will send logged events to your SNMP Trap server.
 
SNMP trap settings
 
SNMP Enabled
If selected, system logs are forwarded as SNMP traps to a trap recipient.
SNMP Server
The host name or IPv4 or IPv6 address of the SNMP trap recipient.
Include up to 10 SNMP trap recipients by separating each with a comma ','.
SNMP Community
Community string for your SNMP trap server.
SNMP Severity
The minimum severity level of log events sent as SNMP traps.
 
Informational: Contains normal operational messages. No action is required.
Warning: Contains cautionary messages. No error has occurred but an error may occur if no corrective action is taken.
Critical: Contains fault-finding messages. Corrective action should be taken promptly.
 
Log events of lower severity are not sent.