Traces for a ServiceLast updated on 06 January, 2023
LogicMonitor creates a service using LM Service Insight for each of the received service trace data. LogicMonitor creates this service when you specify the mandatory “service” OpenTelemetry configuration value. If you specify the optional service namespace in the OpenTelemetry configuration, the value is added as a property to each auto-created service and a parent service is created representing this namespace. This is useful when you have applications with multiple underlying services.
For example, you may have an application “ECommerce” with the following underlying services: “Frontend”, “Cart API”, and “DB”. If you instrument the application with the service name as the “service” configuration flag, and “ECommerce” as the “service namespace”, then LogicMonitor creates the following:
- ECommerce service representing the whole application.
- Three services belonging to the ECommerce service:
- Frontend service
- Cart API service
- DB service
- The service names are not case-sensitive within LogicMonitor.
- For each service, the underlying resources with associated trace data are specified as service members.
LogicMonitor automatically creates services for each unique “service” value in the forwarded traces. For each service, LogicMonitor automatically monitors the Duration, ErrorOperationCount, OperationCount, and UniqueOperationCount metrics:
|Duration||The average time taken by all operations within the service|
|ErrorOperationCount||The number of error operations|
|OperationCount||The total number of operations within the service|
|UniqueOperationCount||The number of unique operations within the service|
For each Service that represents a namespace, LogicMonitor monitors the following aggregated metrics:
|total requests||The total number of requests for all operations in the Services|
|request rate||The average request rate for all operations in the namespace|
|total errors||The total number of errors across all operations in the namespace|
|error rate||The average error rate for all operations in the namespace|
|average duration||The average duration across all operations in the namespace|
|max duration||The max duration across all operations in the namespace|
|95th percentile duration||The 95th percentile duration calculated across all operations in the namespace|
You can set static or dynamic thresholds on these metrics globally when defining the DataSource, at the group level, or for a specific resource.
Recommendation: Set the dynamic thresholds for Duration and ErrorOperationCount metrics to ensure you are notified of any issues with your applications. For more information, see Alerting on Trace data.