Event log entries

Log entries that are forwarded to a destination are formatted in a way appropriate for the specific destination whether it be recorded to a file or sent as an SNMP trap, but log event entries have common elements or properties. All application generated events have the following properties:

The general format for an event in an event log with either a memory, console or file destination is as follows.

nnnn <time> TZONE <severity>: <application> #<event-id> <vrtr-name> <subject> 
<message>

The following is an event log example:

252 2013/05/07 16:21:00.761 UTC WARNING: SNMP #2005 Base my-interface-abc
"Interface my-interface-abc is operational"

The specific elements that compose the general format are described in Table: Log entry field descriptions.

Table: Log entry field descriptions
Label Description

nnnn

The log entry sequence number.

<time>

YYYY/MM/DD HH:MM:SS.SSS

YYYY/MM/DD

The UTC date stamp for the log entry:
  • YYYY: Year
  • MM: Month
  • DD: Date

HH:MM:SS.SSS

The UTC time stamp for the event:
  • HH: Hours (24 hour format)
  • MM: Minutes
  • SS.SSS: Seconds

TZONE

The timezone (for example, UTC, EDT) as configured by configure log log-id x time-format.

<severity>

The severity levels of the event:
  • CLEARED: a cleared event (severity number 1)
  • INFO: an indeterminate/informational severity event (severity level 2)
  • CRITICAL: a critical severity event (severity level 3)
  • MAJOR: a major severity event (severity level 4)
  • MINOR: a minor severity event (severity level 5)

  • WARNING: a warning severity event (severity 6)

<application>

The application generating the log message.

<event-id>

The application’s event ID number for the event.

<vrtr-name>

The router name (vrtr-name, for example, vprn101 or Base), in a format used by the logging system, representing the router instance that generated the event.

<subject>

The subject/affected object for the event.

<message>

A text description of the event.