OpenTelemetry Tracing

With the help of Coralogix’s integration with Jaeger, you can now monitor trace information using Coralogix. Keep an eye on requests which allow you to monitor latency, and know how much time a request would take to finish.

You will also be able to better troubleshoot, pinpoint bottlenecks, and identify which service or services are contributing to the application latency.

Prerequisites

• Have OTELCol (OpenTelemetry Collector) installed (https://opentelemetry.io/docs/collector/getting-started)

Configuration

In order to configure Jaeger to send trace information to Coralogix, edit the OTELCol configuration file and add the Coralogix Exporter config to the exporter section.

exporters:
  coralogix:
    # The Coralogix traces ingress endpoint
    endpoint: "tracing-ingress.coralogix.com:9443"

    # Your Coralogix private key is sensitive
    private_key: "xxx"

    # Traces emitted by this OpenTelemetry exporter should be tagged
    # in Coralogix with the following application and subsystem names
    application_name: "MyBusinessEnvironment"
    subsystem_name: "MyBusinessSystem"

Your private_key, can be found in your Coralogix account under:

• Data Flow
• API Keys
• Send your logs

Make sure to have the correct endpoint in your configuration:

Once you’ve followed these steps to send Jaeger data to Coralogix, begin to use Jaeger tracing data as part of your workflow with Coralogix. You can reach the Jaeger UI directly from the Coralogix navigation or from a specific log in the Logs Screen to view the relevant flow, request time, and the different services that were executed. Learn more about Tracing in Coralogix.

Our support team is always here 24/7 to assist you with anything you need. Send us an email to [email protected], or simply log in to your account and send us a message via our in-app chat.