Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Kiwi Syslog Server > Action - Log to NT Event log

Action - Log to NT Event log

Updated May 9th, 2016


This article describes logging the syslog message to the NT application event log whenever a message is received and passes the filters set.


All supported Kiwi Syslog Server versions


The NT event log has five logging levels:

  • Error
  • Warning
  • Information
  • Success Audit
  • Failure Audit

Select a logging level from the Event log message type drop down list. Messages will then be logged to the NT event log with this selected level.

Setting the log insertion type:

When the message is inserted into the Event Log it can be done in three ways. The messages are logged as follows:


  1. Single insertion string
    %1 is replaced with:
    Date – Tab – Time – Priority – Tab – Hostname – Tab – Message

  2. 5 Tab delimited insertion strings
    %1 Tab %2 Tab %3 Tab %4 Tab %5
    %1 = Date
    %2 = Time
    %3 = Priority
    %4 = Hostname
    %5 = Message

  3. 5 Space delimited insertion strings
    %1 Space %2 Space %3 Space %4 Space %5
    %1 = Date
    %2 = Time
    %3 = Priority
    %4 = Hostname
    %5 = Message


Click Test to check the NT event logging action. When running on a non-NT system, like Windows 95/98, no message will be logged and you may receive an error message.


Note: By default, when viewing the NT event log with the NT event log viewer, the log type is set to show System events. To show Application events, you need to check the Application item in the Log menu of the NT Event viewer.




Last modified