AIOps Value dashboard

As an operator or site reliability engineer (SRE), use the AIOps Value dashboard to view the key performance and operational metrics for alarm and anomaly events, and assess how effectively situations help improve incident handling, reduce noise, and accelerate issue identification and resolution over time.

The dashboard displays key performance indicators such as event noise reduction, incident noise reduction, mean-time-to-resolve (MTTR), and mean-time-to-identify (MTTI). Additional operational metrics provide insights into events related to and not related to situations, associations, and correlation accuracy across services.

Operators or SREs can use this dashboard to:

Get real-time visibility into how BMC Helix AIOps improves service reliability and operational performance.
Identify efficiency trends in event correlation, detection, and resolution over time.
Make data-driven decisions to proactively optimize service performance and operational efficiency.
Reduces manual effort by offering an out-of-the-box, ready-to-use view—no custom dashboard setup needed.

Example: Analyze and get insights from key performance and operational metrics

Jim, an SRE in Apex Global, wants to get insights from the performance indicators analysis for the last 15 days to identify the most impacting issues or impacted services.

He performs the following steps to get the required information:

Jim logs in to BMC Helix Dashboards and opens the AIOps Value Dashboard.
In the time range filter, he selects Last 15 days.
(Optional) In the Event Type filter, he selects all types of events from the alarm and anomaly event types.

Jim views the % Event Noise Reduction, % Incident Noise Reduction, Mean Time to Resolve, and Mean Time to Identify panels to understand how efficiently situations are reducing operational noise, improving incident management, and accelerating issue detection and resolution over time.

The operational KPIs panel displays metrics such as total events, total situations, events that are part of situations, the percentage of events that are part of situations, events not part of situations, events with node association, events with service association, the percentage of events with service association, and events with errors. These metrics serve as the foundation for calculating the business KPIs, providing insights into how situations improve service reliability and reduce operational noise.

The following image shows the AIOps Value Dashboard with sample data:

To view the AIOps Value dashboard

View the AIOps Value dashboard in one of the following ways:

Viewing from BMC Helix Dashboards:

Log in to BMC Helix Dashboards.
From the navigation menu , click Dashboards.
In the Service Dashboards folder, click AIOps Value Dashboard.

Tip: Quick access from the home page

To quickly open the dashboard from the home page, mark it as a favorite by using the star icon. Additionally, after you open a dashboard, it is available under Recently viewed dashboards on the home page.

Panels in the AIOps Value dashboard

The following table describes the panels in the AIOps Value dashboard:

Panel	Description	Example
Dashboard filter	By default, the dashboard displays the data for the last 30 days. You can filter the data by using the time range global filter for up to the last 90 days.
Event Type filter	Allows you to filter the data based on Alarm, Anomaly, or All event types.
Business KPIs
% Event Noise Reduction	Displays how the overall event noise is reduced by correlating related events into situations. Formula: Event noise reduction (%) = (E - (S+SA)/E) × 100 Event noise reduction (%) = (Total number of events - (Number of situations formed+Number of standalone events)/Total number of events) × 100 where: E = Total number of events S = Number of situations formed SA = Number of standalone events (that are not part of any situation)
% Incident Noise Reduction	Displays how the number of incidents created from correlated events is reduced. A higher incident noise reduction percentage indicates that duplicate or unnecessary incident creation is reduced by grouping related events into situations. This helps teams focus on fewer, more meaningful incidents, improving productivity and service response time. Formula: Incident Noise Reduction (%) = ((Events qualified for incidents−incidents formed)/Events qualified for incidents)×100 where, Events qualified for incidents = Number of events that meet the criteria to trigger incidents Incidents formed = Number of actual incidents created after correlation If the policy for incident criteria is disabled, the incident noise reduction value is zero.
Mean Time To Resolve	Displays the average time taken to resolve an issue after it has been identified. It reflects the end-to-end efficiency of the operations team in remediating the issue and restoring normal service. In BMC Helix AIOps, MTTR is measured from the moment a situation is identified (or a ticket is created) until the situation is closed or the fix is applied and confirmed. Lower MTTR values indicate faster remediation, improved operational performance, and effective use of situations to accelerate incident resolution. Important: MTTR is a global business KPI computed from situations only. Even when filtering by specific event types (e.g., Anomaly), the MTTR value displayed represents the global situation-level metric across all event types. If no situations are formed for the selected event type, the displayed MTTR still reflects the overall situation performance, not event-specific data. Formula: MTTR = ∑(Time resolved−Time identified)/Number of situations where, Time identified = Timestamp when the correlated situation is formed Time resolved = Timestamp when the situation is closed Note: If the selected Event Type filter shows "Events part of Situation = 0", this indicates no situations were formed from that event type, but the MTTR value displayed is still the global situation metric, not specific to that event type. In such cases, interpret the MTTR as the overall system performance, not as metrics for the filtered event type.
Mean Time To Identify	Shows the average time taken to detect and correctly identify an issue or anomaly in the monitored environment. In BMC Helix AIOps, this metric is calculated from the moment the first relevant event is ingested until the events are correlated into a situation and classified as actionable. A lower MTTI indicates faster detection, better operational efficiency, and effective event correlation in situations. Important: MTTI is a global business KPI computed from Situations only. Even when filtering by specific event types (e.g., Anomaly), the MTTI value displayed represents the global situation-level metric across all event types. If no situations are formed for the selected event type, the displayed MTTI still reflects the overall situation performance, not event-specific data. Formula: MTTI = ∑(Time identified−Time first event occurred)/Number of situations where, Time first event occurred = Timestamp when the first relevant event for that situation was ingested. Time identified = Timestamp when the correlated situation is formed. Note: If the selected Event Type filter shows "Events part of Situation = 0", this indicates no situations were formed from that event type, but the MTTI value displayed is still the global situation metric, not specific to that event type.
Operational KPIs
Total Events	The total number of events ingested by BMC Helix AIOps within the selected time range. This includes all events, whether correlated into situations or standalone.
Total Situations	The total number of situations created by BMC Helix AIOps by correlating related events using ML and topology-based analysis.
Events part of situations (Event Correlation Coverage)	The total number of events that have been correlated into situations. These represent meaningful event groups that indicate potential root causes or service-impacting issues.
% Events part of Situations (Event Correlation Coverage)	The percentage of total events that are correlated into situations. %Events part of situations=(Events part of situations/Total events)×100 A higher percentage indicates better event correlation coverage and lower operational noise.
Events not part of Situations	The total number of standalone events that are not correlated to any situation. These are typically low-impact or isolated events that did not meet correlation criteria.
Events with Node Association	The number of events that have a node (infrastructure element) linked in the BMC Helix Discovery and a service model. These events can be mapped to infrastructure components.
Events with Service Association (Qualified events for AIOps)	The number of events associated with a business service. These are qualified events for BMC Helix AIOps analysis, as they can be tied directly to service health and impact.
% Events with Service Association (Qualified Events for AIOps)	The percentage of total events that are associated with a service. %Events with Service Association=(Events with Service Association/Total Events)×100 A higher percentage indicates better service-context awareness in event data.
Events with Errors	The count of events that contain data errors or missing associations (such as missing node or service information) that may affect correlation or analysis accuracy.
Raw data	Displays Total events with the following details: Creation time: The date and time stamp of the event creation. Errors: Indicates whether any errors were encountered in the event payload, such as missing or malformed fields, incorrect associations, or ingestion issues. Identifier: A unique ID assigned to each event. Impacted service: The name of the business service impacted by the event. Node id: The unique identifier of the node (host, VM, or device) from which the event originated. Relationships mlsituation: Represents the relationship between an event and the situation it belongs to. If populated, it indicates that the event is correlated into a situation. Relationships rstat: Indicates the relationship status or state of the event in relation to other events or situations. Service id: A unique identifier of the impacted service. Service key: The internal key used by BMC Helix AIOps to link the event to a specific service entity in the database or service model. Service name: Name associated with the service created in BMC Helix AIOps or discovered in BMC Helix Discovery. Tenant ID: Identifies the tenant or account to which the event belongs.

FAQs

Why do I see MTTR or MTTI values when filtering by Anomaly event type, even though no situations are formed (Events part of situation=0)?

MTTR and MTTI are global business KPIs calculated from all situations, regardless of the Event Type filter selection. These metrics are situation-level performance indicators and are not filtered by event type.

When you filter by an event type that does not form situations (e.g., INFO-severity Anomalies), the operational KPIs will correctly show Events part of situation=0 for that event type. However, the business KPIs (MTTR or MTTI) continue to display the global situation metrics across all event types.

This is because:

Business KPIs measure overall system performance and situation handling efficiency
Operational KPIs provide event-type-specific metrics
Dashboard panels cannot be conditionally hidden based on filter selections

Which metrics are affected by the Event Type filter?

The Event Type filter affects operational KPIs like Total Events, Events part of situations, Events not part of situations, Events with Node Association, Events with Service Association, Events with Errors, and the raw data table.