Question & Answer
Question
How does the generic clear trigger function?
Cause
The Object Server requires the event model to reduce the active event volume automatically.
Answer
Description
The generic_clear trigger scans the alerts.status table to find all problem events [Type 1 and Severity > 0]
It attempts to match these events to the resolution events [Type 2 and Severity > 0] that have arrived in the object server since the last time it was run.
The generic_clear trigger clears any matching problem events, and all the resolution events.
It attempts to match these events to the resolution events [Type 2 and Severity > 0] that have arrived in the object server since the last time it was run.
The generic_clear trigger clears any matching problem events, and all the resolution events.
Generic clear event matching is based on the condition.
Events that have the same Node value AND
Events that have the same Manager value AND
Events that have the same AlertGroup value AND
Events that have the same AlertKey value
Events that have the same Manager value AND
Events that have the same AlertGroup value AND
Events that have the same AlertKey value
Note: Problem and resolution events usually have the same @Identifier with the @Type field value added to the event to create two unique events.
@Identifier = @Node + ':' + @Manager + ':' + @AlertGroup + ':' + @AlertKey + ':' + @Type
| Field | Comment |
| @Node |
The events source node name
e.g. The element managers server name |
| @Manager | The events source manager name e.g. The probes name |
| @AlertGroup | A string that defines the events grouping e.g. The source element manager |
| @AlertKey |
A string that defines the event uniquely
e.g. The alarm identification number |
| @Type |
An integer that defines the events type
e.g. 1 for problem, 2 for resolution |
The other generic_clear fields are
o Severity
o LastOccurrence
o LastOccurrence
Severity must be set to a value greater than zero, with the Resolution [@Type=2] event having a @Severity of indeterminate [@Severity=1] and the Problem [@Type=1] event having a @Severity of greater than clear [@Severity=0].
For a Problem event to be cleared it's Resolution event must have a LastOccurrence greater than Problem events LastOccurrence.
The deduplication trigger discards any events that have older LastOccurrence and ProbeSubSecondId values that are not greater than the current event in the object server
o The expire trigger clears any events whose expire time has been reached
o The delete_clears trigger deletes any clear event that has a StateChange value older than 2 minutes
In the multitier environment the standard triggers are replaced by layer specific triggers.
e.g. col_new_row, col_deduplication, col_expire
Overview of the generic_clear trigger
o Run every 5 seconds
o Populate the alerts.problem_events table with all problem events that have a corresponding resolution event in alerts.status
o For each resolution event, in alerts.status, mark the corresponding alerts.problem_events entry as resolved
o Clear all the resolution events in alerts.status
o Clear all resolved problem events in alerts.status
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"ARM Category":[{"code":"a8m500000008aAZAAY","label":"Core Omnibus-\u003EObjectServer nco_objserv-\u003EOS - Common Triggers"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.0"}]
Was this topic helpful?
Document Information
Modified date:
21 May 2025
UID
ibm17233252