Event Log Listing

Event Log Listing (kourier_eventlog_listing.aspx)

Purpose

Use this report to display the events generated by Kourier Integrator. Some of these events are informational and largely ignored. Others, however, are worthy of immediate attention. Any one of these events can trigger a filter that can notify a user via e-mail or suppress the event from being logged.

File/Key Field

KT_LOG/ID

Prerequisites

The Event Log Configuration needs to be setup correctly in order to generate events at the level you wish to see them.

Cautions

None.

Report Filters

There are no Quick Filters on this listing. Click the filter icon in the command bar to enter Event Log filter criteria.

Report Fields

ID	Displays the order sequence for the event log filter. You can click the ID to see all of the information for the event in form view. This can be helpful when you want to see all of the text for a long event message.
Date	The date the event was logged.
Time	The time the event was logged.
Type	The type of event severity (ERR, WARN, INFO, TRACE, DEBUG, VERBOSE).
Service	The name of the Kourier service (if any) that was running when the event was logged.
Run	The run number for the event. This groups all events within one run number so it's easy to see everything that happened during the run.
Source	The name of the program or subroutine that must generate the event. Typical values here are: KMK.SERVICE, KMK.DEQMSG, KMK.TRACE, KMK.EXPORT, KMK.EXPORTEXEC, KBO.SYSTEM.
Event	The Event ID that was generated. This can be used to trigger event notifications.
Message	This is the actual text of the event. It will usually be a very verbose message and will include a detailed description of exactly what occurred in the event. It is very helpful in seeing what the Kourier system is has done and how it does it. This information will be helpful while trying to diagnose system or data issues.
User ID	[Form view only] Displays the user id of the person logged in when the event was generated. This will be KOURIER when the system is run from the GUI, which is most of the time. However, if any of the Kourier commands, services, etc. are run from TCL, the user id will show who was logged in at that time.