Viewing Traces for a Service

LogicMonitor creates a service (via LM Service Insight) for each service trace that data is received for (using the mandatory “service” OpenTelemetry configuration value). If you specify a service namespace (an optional configuration flag in the OpenTelemetry spec), it will be added as a property to each auto-created service and a parent service will be created representing this namespace. You may find this useful organizationally where you have applications with multiple underlying services.

For example, you may have an application “ECommerce” with multiple underlying services: “Frontend”, “Cart API”, and “DB”. If the auto-instrumentation for these services is done such that the service name is used for the “service” configuration flag, and “ECommerce” is used for the “service-namespace”, then LogicMonitor will create four things:

1. A service named ECommerce representing the whole application
2. Three services belonging to the ECommerce service: Frontend, Cart API, and DB

Note that the service names are case-insensitive within LogicMonitor. For each service, the underlying resources that the trace data is associated with, if specified in the trace data (this is optional information per OpenTelemetry), will be specified as service-members.

Service-level traces

LogicMonitor automatically creates Services for each unique “service” value in the forwarded traces. For each Service, LogicMonitor automatically monitors four metrics: Duration, ErrorOperationCount, OperationCount, and UniqueOperationCount.

For each Service that represents a namespace, LogicMonitor monitors the following aggregated metrics.

You can set static or dynamic thresholds on these metrics in the same way as any other metrics within LogicMonitor: globally when defining the DataSource, at the group level, or for a specific resource. We recommend setting dynamic thresholds for Duration and ErrorOperationCount metrics to ensure you are notified of any issues with your applications. See Alerting on Trace data.