Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Creating Events from Application Server (Advanced)


It is possible to create user events from the application server to the Event Browser. This feature may be useful for user specific customization, automation, or reporting. To do this a command line utility is available on the server in the /u/wandl/bindirectory. The utility is called .eventcli (note that the utility is a hidden file).

Post Single Event

To post a single event, run the following command on the server:

  • <eventType> corresponds to Event Browser Type field. It is case sensitive and must match one of the predefined types. A list of these event types can be found in the Event Browser > Post Network Event window in the Type field. This field is required.

    Figure 1: List of Event Types
    List of Event Types
  • <elementType> are Element Types such as Node, Protocol, Tunnel. You may create your own entry.

  • <deviceID> is the Device ID of the router or equipment. You may create your own entry even if the device is not part of the network.

  • <elementName> is the Element Name. You may create your own entry.

  • <Severity> levels are mapped as follows:

    • UNDEFINED = -1

    • INFO = 1000. This is the default value if left blank or mapped incorrectly.

    • NORMAL = 2000

    • UP = 2001

    • WARNING = 3000

    • MINOR = 4000

    • MAJOR = 5000

    • CRITICAL = 6000

    • DOWN = 6001

  • <sourceIP> is the source IP address. You may create your own entry.

  • <description> is the Description field. You may create a string using double quotes.

Example post single event command:

Only the <eventType> field is required to post an event. If the other parameters are not specified, then the values will simply be blank and use the default INFO severity level.

Post Multple Events

To post multiple events, run the following command on the server:

/u/wandl/bin/.eventcli batch <batchcmd_file>

<batchcmd_file> = This is a text file with a list of commands using the same syntax described in Post Single Event. Use one command per line.

Example batch command text file:

You may use the # symbol in the file for comments which are ignored by the utility.