Integration Server 11.1 | Integration Server Administrator's Guide | Managing Event Triggers | Runtime Perspective for Event Triggers
 
Runtime Perspective for Event Triggers
Use the Runtime Perspective on the Streaming > Event triggers page to view detailed, unified statistics for all of the consumers for running event triggers. The provided details might help identify where processing issues are located.
Field
Description
Name
Fully qualified name of the event trigger.
State
Indicates whether the trigger is enabled, disabled, or suspended. Click the trigger state to access the New state option that you can use to enable, disable, or suspend the event trigger.
Last Trigger Status Change
Time elapsed since the trigger status last changed.
The status reflects the current condition of the trigger. An event trigger can have a status of “Running” or “Not Running (reason)” where reason identifies why the trigger is not running, such as “Not Running (Trigger Disabled)” or “Not running (Connection Alias Not Running)”.
Connection Alias
Streaming connection alias used by the event trigger.
Consumer ID
Unique identifier for the consumer.
Topic Partition
Partition from which the consumer received an event. If the event trigger has multiple consumers, one partition is listed for each consumer.
Consumer Status
Status of the consumer, either Requesting Events or Processing Events.
Last Consumer Status Change
Time elapsed since the consumer changed status, which indicates how long a consumer has had a particular status. If a consumer has been in the same state for a long period of time, it might indicate an issue.
Received
Number of events received by the consumer since the trigger was enabled.
Pre-Processing
Number of events currently in pre-processing by this consumer where pre-processing refers to the FILTER and TRANSFORM intermediate stream processing steps.
Buffered
Number of events in the buffer, waiting to be flushed or processed by the consumer. Events in the buffer have undergone pre-processing by an intermediate stream processing step and, for event triggers that process a window of events, processing by a terminal stream processing step (COLLECT or CALCULATE).
Filtered
Number of events filtered out by the FILTER processing step since the trigger was enabled.
Error
Number of events received by the consumer where processing ended in error. Integration Server drops these events.
Dropped
Number of events received by this consumer that were dropped since the trigger was enabled. Integration Server may drop an event because the event is a duplicate or was received outside of the grace period for a time-based window. The Dropped value does not include events dropped due to an error.
Processing
Number of events currently being processed by the consumer. Events which have completed pre-processing remain in "processing" until the final stream processing step completes (INVOKE_TARGET or FORWARD_TO_TOPIC).
Processed
Number of events processed by the consumer since the event trigger was enabled.
Last Received
Time elapsed since the consumer most recently received an event.