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!
You can use the following methods for OpenTelemetry-facilitated instrumentation of a .NET application:
Depending on your environment, you may need a combination of both manual and automatic instrumentation.
To instrument a .NET application, you must install and configure an OpenTelemetry Collector to forward trace data to your LogicMonitor portal. For more information, see Installing an OpenTelemetry Collector.
Note: LogicMonitor requires the following custom tags to map traces to existing monitored resources: ip, resource.type (which should be set to kubernetes-pod, cloud, or host), and host.name (which should be the pod name for Kubernetes). Use these custom tags when possible to ensure that traces are shown in the context of logs, metrics, and alerts.
Note: If your OpenTelemetry Collector was installed on a different server, you may need to update the value of Dotel.export.otlp.endpoint from localhost to the IP of the server where the OpenTelemetry Collector is running.
Dotel.export.otlp.endpoint
You can manually instrument your .NET applications if you are using applications that are not supported for the OpenTelemetry automatic instrumentation or if you want to customize how traces are generated by automatic instrumentation (For example, how operations are named).
For more information about manually instrumenting your .NET application, the OpenTelemetry SDK, creating and enriching traces, see OpenTelemetry’s Manual Instrumentation documentation.
In This Article