Monitoring services and identifying application issues

Use BMC Helix AIOps to monitor service health and BMC Helix Dashboards to analyze traces and metrics.

Before you begin

Make sure that you have enabled BMC Helix applications to ingest telemetry data from OpenTelemetry. For more information, see Ingesting data from OpenTelemetry.

To monitor service health and identify application issues

1. Log on to BMC Helix AIOps and open the Services page.
2. Search for and then click the parent business service of the service model that you have created while ingesting data from OpenTelemetry. 
   The following example shows that the service has been impacted due to events. These events are generated due to the alarm policy defined for the Error (count) metric. The value of this metric has been more than 2 for more than 1 minute.
   
3. Click a causal node (indicated by the Error icon) responsible for the poor health of the business service. 
   The Node Details pane shows the list of impacting events on the Events tab.
4. On the Events tab, click the event to show the Event Details page.
   The event description indicates that the value of the Error (count) parameter has been more than 2 for more than 1 minute.
5. To identify the erroneous operation, close the Event Details pane, and then click the View OTel Dashboard link.
   The OTel Service Overview dashboard opens in the BMC Helix Dashboards console.
   
6. From Status Filter, select STATUS_CODE_ERROR.
7.  In the Traces for <OTelServiceName> section, sort the Status column and click the ERROR link for any trace. 
   The OTel Trace Details dashboard opens in the BMC Helix Dashboards console.
8. In the Details for TraceID section, expand Service & Operation.
9. Locate the rows containing the error icon .
10. Expand the row and click Span Attributes. 

11. In the right pane, under events, an exception message indicates the issue with the application, as shown in the following example: