Understanding logging in OMS
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. Starting in the dashboard, click System > Log.
2. Type in the Filter 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. OMS can send messages to your Syslog server.
To send log events and alarm notifications, first configure your server and recipient settings. After configuring these settings, you can enable and disable the sending of automated messages.
Configure your server settings:
1. Starting in the dashboard, click System > Settings.
2. In the Feature Settings pane, click Notification.
3. Select Configure a Syslog Server.
4. Configure the options.
For details, use the information in Syslog settings.
5. Click the accept icon .
Enable the sending of log events and alarm notifications:
6. In the Feature Settings pane, click Log.
7. Select Export logged events to a Syslog server.
8. Configure the options.
9. Click the accept icon .
 
OMS will send logged events to your Syslog server.
 
Syslog settings
 
Export logged events to a Syslog server
If selected, system logs are forwarded to a Syslog server.
System logs remain accessible through the dashboard and CLI interfaces.
Target IP address
The host address of the Syslog server.
Include up to 10 Syslog servers by separating each with a comma ','.
Target port
The port number of the Syslog server.
If more than one Syslog server is specified, this port is used for each.
Format
Sets which Syslog protocol is used.
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 OMS log can be sent as SNMP traps. Doing so allows you to monitor OMS 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. After configuring these settings, you can enable and disable the sending of automated messages.
Configure your server settings:
1. Starting in the dashboard, click System > Settings.
2. In the Feature Settings, click Notification.
3. Select Configure an SNMP Trap.
4. Configure the options.
For details, use the information in SNMP trap settings.
5. Click the accept icon .
6. In the Feature Settings pane, click Log.
7. Select Export logged events to an SNMP Trap.
8. Configure the options.
9. Click the accept icon .
 
OMS will send logged events to your SNMP Trap server.
 
SNMP trap settings
 
Export logged events to an SNMP Trap
If selected, system logs are forwarded as SNMP traps to a trap recipient.
Target IP address
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 ','.
Target port
The port number of the SNMP trap recipient.
Example: 162
If more than one SNMP trap recipient is specified, this port is used for each.
Community String
Community string for your SNMP trap server.
SNMP version
Sets the SNMP trap version.
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.
 
How to send e-mail alerts
To send log events and alarm notifications, first configure your server and recipient settings. After configuring these settings, you can enable and disable the sending of automated messages.
Configure your server settings:
1. Starting in the dashboard, click System > Settings.
2. In the Feature Settings, click Notification.
3. Select Configure an Email Server.
4. Configure the options.
For details, use the information in E-mail settings.
5. Click the accept icon .
Enable the sending of log events and alarm notifications:
6. In the Feature Settings pane, click Log.
7. Select Export logged events via email.
8. Configure the options.
9. Click the accept icon .
 
OMS will send logged events to your SMTP server.
 
E-mail settings
 
Export logged events via email
If selected, system logs are forwarded as email messages.
SMTP Server
The host address of the outgoing email server.
Example: 203.0.113.12 -or- smtp.example.com
Valid Input: Valid addresses include IPv4 or DNS name.
SMTP Port
The port number of the outgoing email server.
Security
The connection to the outgoing email server can be encrypted to prevent eavesdropping.
 
PlainText Connection is not encrypted.
SSL, TLS, or DTLS Connection is encrypted.
STARTTLS Negotiates an encrypted connection. If negotiation fails, the connection is not encrypted.
 
Authentication
The authentication type for connecting to the outgoing email server.
Try choosing 'Auto Detect' if you experience authentication problems.
User Name
The user name used to connect to the outgoing email server.
Password
If 'User Name' requires a password to connect, type the password here.
Leave this box blank if 'User Name' does not require a password.
Sender Name
If specified, this sender name appears in the 'From' field of the sent email.
Setting Sender Name to 'OMS Security' or similar could help recipients categorize the emails.
Sender Email
The sender email address appears in the 'From' field of the sent email.
Recipients Email
Log events are sent to the specified email address or addresses.
Example: chris@example.com -or- chris@example.com;pat@example.com
Email multiple recipients by separating each address with a semi-colon ';' or comma ','.
Severity
The minimum severity level of log events sent as email messages.
 
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 return to the default log settings
You can return the event log to its default settings if necessary. The default behavior is to not forward any log events to email, SNMP, or Syslog, so these will be disabled in the process.
To return to the default log settings:
1. Starting in the dashboard, click Config > .
2. In the Feature Settings pane, click Logs.
3. Click the reset icon .
4. Click the accept icon .
 
The log settings have been returned to their default settings.