Join fellow LogicMonitor users at the Elevate Community Conference and get hands-on with our latest product innovations.

Register Now

Resources

Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

View Resources

About us

Get to know LogicMonitor and our team.

About us

Documentation

Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

View Resources

Trace Data Forwarding from Externally Instrumented Applications

Last updated on 07 November, 2024

If you did not use LogicMonitor to instrument your applications, you can modify the receiver value in the OpenTelemetry Collector configuration to forward traces to LogicMonitor. This enables the collector to receive traces in the format that the application was instrumented in, and then forward the traces to LogicMonitor in OpenTelemetry format via otlphttpexporter.

Forwarding Traces from Externally Instrumented Applications

Note: The following uses Jaeger as an example receiver value. Reference the applicable documentation from the libraries you used to instrument your applications.

In the OpenTelemetry Collector configuration, modify the receiver value to use the library you used to instrument your application, similar to the following:

receivers:
  jaeger:
    protocols:
      grpc:
      thrift_http:
exporters:
  otlphttp:
    endpoint:https://${LOGICMONITOR_ACCOUNT}.logicmonitor.com/rest/api/vi/traces
    headers:
      Authorization: Bearer ${LOGICMONITOR_BEARER_TOKEN}
service:

  extensions: [nop]
  traces:
    receivers: [jaeger]
    exporters: [otlphttp]

Traces display in your LogicMonitor portal when the application emits the traces.

In This Article

Get Started with LogicMonitor