Introduction to Syslogs and Traps

Download this manual as a PDF file

This section describes how Syslog and SNMP Trap messages are processed by Skylar One appliances that perform Message Collection.

Use the following menu options to navigate the Skylar One user interface:

  • To view a pop-out list of menu options, click the menu icon ().
  • To view a page containing all of the menu options, click the Advanced menu icon ().

Appliances that Process Syslog and SNMP Trap Messages

In Skylar One, three types of Appliances can process Syslog and SNMP Trap messages from monitored devices. The following appliances can perform the Message Collection function:

  • All-In-One Appliances
  • Message Collectors
  • Data Collectors

A Data Collector can perform Message Collection only if that Data Collector is in a Collector Group that contains no other Data Collectors

For more information about Skylar One appliances functions and architecture, see the section on Architecture.

For information on how to create a collector group, see the section on Collector Groups.

Multi-byte Character Support

Skylar One supports inbound syslog and SNMP trap messages that include multi-byte characters. Multi-byte characters can be displayed in the following pages:

  • The Events page and Event Console page (Events > Classic Events, or the Events tab in the classic user interface) can display multi-byte characters in syslog and SNMP trap event messages.
  • The Device Logs & Messages page (the Logs tab on the Device Investigator, the Device Administration panel, and the Device Reports panel) can display multi-byte characters in syslog and SNMP trap log messages.
  • The Ticket Description and Ticket Notes fields in the Ticket Editor page can display BMP characters populated from an event message by an automation action. SMP characters are not supported in these fields.

Multi-byte characters can be included in the following fields and functions:

  • Outbound SNMP Trap messages generated by the automation engine can now include an event message that contains multi-byte characters.
  • Multi-byte characters can be included in the Event Message, First Match, Second Match, and Identifier Pattern fields in the Event Policy Editor page.
  • Multi-byte characters can be included in the Varbind OID Pattern field in an SNMP Trap Filter (Evnts > SNMP Trap Filters, or Registry > Events > SNMP Trap Filters in the classic user interface).
  • Multi-byte characters can be included in the Expression Match field in a Redirect Policy (Redirects tab on the Device Investigator and the Device Administration panel).