Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Forwarded traces are automatically mapped to the monitored resources if sufficient information (such as host.name, ip, resource.type, and resource.group) is provided during instrumentation and the resources exist. If the resources don’t exist, new resources will be automatically created.
For each Resource, the following three DataSources will be automatically applied: RootServices, Services, and Operations. See the sections below for more details.
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.
The RootServices DataSource monitors metrics that are specific to the services running on the resource which initiates the trace. Each root service is represented by a LogicMonitor instance, and the following metrics are monitored:
The Services DataSource monitors metrics that are specific to each service running on the resource, regardless of whether it is a service which initiated the trace or passed through. Each service is represented by a LogicMonitor instance, and the following metrics are monitored:
The Operations DataSource monitors metrics specific to each of the operations within the services running on the resource. Each operation is represented by a LogicMonitor instance, and the following metrics are monitored: