IBM Support

Enabling EventReader debug

Troubleshooting


Problem

How to determine if certain events are actually being captured by the EventReader?

Resolving The Problem

Putting the EventReader in debug enables the EventReader debug logging to capture the Serial and StateChange value of every event captured. This requires an additional property in the ImpactServer properties file:

    $NCHOME/impact/etc/[ImpactServerName]_server.props

to capture the Serial and StateChange of all events captured by the EventReader(s):

    impact.eventreader.debug=true

This will require an ImpactServer restart to enable and you will then see the additional log statements of the format:

    [DateTimeStamp]: New Event -> Serial: 12345 StateChange: 1234567890

Where [DateTimeStamp] is the date and time the log message was recorded in the format:

    day month year hours:minutes:seconds,milliseconds

This is in the log files for your EventReader Services:

    $NCHOME/impact/log/[ImpactServerName]_[EventReaderName].log(.n)


Or, for Impact 6 & 7:

    $NCHOME/impact/logs/[ImpactServerName]_[EventReaderName].log(.n)

Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [EventReaderName] is the name of the EventReader Service producing this output (for example: omnibuseventreader) and (.n) are the numbered roll-over log files (between 1 and 10 by default).

Please also ensure that the EventReader is configured to log to file - for example:


[{"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Netcool\/Impact","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"}],"Version":"6.1;6.1.1;7.1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21596162