Log events that are forwarded to a destination are formatted in a way that is appropriate for the specific destination; for example, whether it is to be recorded to a file or sent as an SNMP trap. However, log events also have common elements or properties. All application-generated events have the following properties:
a timestamp in UTC or local time
the generating application
a unique event ID within the application
a router name identifying the VRF ID that generated the event
a subject identifying the affected object
a short text description; for further information about variables found in the message format strings, see the associated SNMP Notification definition in the 7705 SAR MIBs
The general format for a log event with a memory, console, or file destination is as follows.
nnnn YYYY/MM/DD HH:MM:SS.SS TZONE <severity>: <application> #<event_id> <router-
name> <subject> <message>
The following is a log event example:
252 2017/05/07 16:21:00.76 UTC WARNING: SNMP #2005 Base my-interface-abc
"Interface my-interface-abc is operational"
The specific elements that make up the general format are described in the following table.
Label |
Description |
|---|---|
nnnn |
The log entry sequence number |
YYYY/MM/DD |
The UTC or local date stamp for the log entry YYYY — year MM — month DD — day |
HH:MM:SS.SS |
The UTC timestamp for the event HH — hours (24-hour format) MM — minutes SS.SS — seconds |
TZONE |
The timezone (for example, UTC, EDT) as configured by configure log log-id log-id time-format |
<severity> |
The severity level of the event
|
<application> |
The name of the application generating the log message |
<event_id> |
The application event ID number for the event |
<router> |
The router name representing the VRF ID that generated the event |
<subject> |
The subject/affected object for the event |
<message> |
A text description of the event |