Create an event rule to bind metric events to host CIs
-
- UpdatedAug 1, 2024
- 2 minutes to read
- Xanadu
- IT Operations Management
Create event rules to explicitly allow binding of metric events to host CIs.
Before you begin
About this task
Starting with the London release, Metric Intelligence no longer relies on the default Event Management binding workflow which binds nodes to host CIs. Event Management is configured to apply the default host binding algorithm when an event rule cannot find a CI to bind to, based on event data. In Metric Intelligence, with a given event rule and two different events, there can be a situation where one event binds to the correct CI and another event cannot bind. In this case, the same metric types would be created for the selected CI and for the host level CI, causing confusion.
For example: With an event rule that binds the disk percentage metric to a storage disk, one event can find a disk CI and another event cannot. This results in the disk percentage metric being created for a disk CI and for a host CI.
To avoid this confusion, Event Management default host binding is disabled for metric events in the base system. To allow host binding for metric events, explicitly create the following event rule in the Event Management event rule designer. The underlying binding functionality of the event rule designer is used to map metrics to CIs.
Procedure
- Navigate to to open the event rule designer.
-
Click New and ensure that the
Active toggle switch
is set to the right (Active).
-
On the Event Rule Info tab:
- Set Source to the data source that this rule applies to.
- (Optional) Enter a Description such as Bind metrics at host level.
- On the Event Filter tab, set a filter condition to indicate that Classification is Metric.
- Click Save.
Related Content
- Bind alerts to a CI running on a host using CI identifiers
Create an event rule to bind alerts to a CI running on a host.
- Create or edit an event rule
You can create event rules to generate alerts for tracking and remediation. Use team-based integrations in event rules to make sure that connector ownership and execution of rules give precedence to general rules. Teams can maintain consistency and hierarchy while offering flexibility and customization options.