Our next-gen architecture is built to help you make sense of your ever-growing data Watch a 4-min demo video!

Back to All Integrations

OpenTelemetry Tracing OpenTelemetry Tracing

Last Updated: Jul. 05, 2022

With the help of Coralogix’s Distributed Tracing screen which you can find under Explore, 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. (Check out the documentation page: https://coralogix.com/docs/distributed-tracing/)

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

This manual will explain how to configure the tracing integration.

Prerequisites

  • Have OTELCol (OpenTelemetry Collector) installed with contrib support
    You can find the core source code Here
    You can find the contrib source code Here
  • Have a working Coralogix account.

Configuration

To send your traces to Coralogix you will need to config an Exporter (of the Coralogix type).
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:

RegionTraces Endpoint
USA1tracing-ingress.coralogix.us:9443
APAC1tracing-ingress.app.coralogix.in:9443
APAC2tracing-ingress.coralogixsg.com:9443
EUROPE1tracing-ingress.coralogix.com:9443
EUROPE2tracing-ingress.eu2.coralogix.com:9443

Docker Deployment

If you choose to use a single docker deployment or a kubernetes based deployment you can fetch the relevant image like so:

docker pull ghcr.io/open-telemetry/opentelemetry-collector-releases/opentelemetry-collector-contrib:0.54.0

Kubernetes Deployment

If you wish to deploy Otel as part of your cluster you can also use a helm chart provided by the Open Telemetry community, by running these commands (Docs can be found Here):

helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts
helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector

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.

On this page