groundcover is fully able to ingest traces generated by Datadog APM, displaying it natively in our platform. The result is a seamless experience of combining eBPF and Datadog traces to enable even more insights into your applications.

See below for an example usage of the ingested traces, moving between viewing individual spans to a distributed tracing panel showing the entire trace.

There are two ways to ingest DataDog traces into groundcover:

  1. Redirecting the DataDog SDK to send traces to groundcover's endpoint

  2. Automatically picking up the traces using eBPF

Redirecting the SDKs traces endpoint

This is the recommended way to ingest DataDog traces into groundcover.

If you don't have an active Datadog agent, or you wish to send the traces to groundcover directly - we got you covered. After instrumenting a service with Datadog's SDK, simply redirect your traces to groundcover's ingestion endpoint to see them natively in our app.

Finding the groundcover Alligator Service Endpoint

Use the instructions here to locate the endpoint for the Alligator service, referenced below as {GROUNDCOVER_ALLIGATOR_ENDPOINT}.

Configuring the DataDog SDK

Apply the following environment variables to your deployment to redirect the traffic to groundcover's endpoint for ingestion.

Keep in mind - using this method will stop sending traces to the Datadog agent, meaning they will not appear in Datadog's platform

    value: "http://{GROUNDCOVER_ALLIGATOR_ENDPOINT}:8126"

Automatic ingestion using eBPF

If groundcover is installed in an environment with an active Datadog agent, our eBPF sensor will automatically collect, ingest and display the Datadog traces generated by your services. As simple as that!

It might take a few minutes for traces to appear after installation when using this method. About the average time to make a cup of coffee

Automatic ingestion is turned off by default, but can be turned on using the following overrides:

        proxyEnabled: true

Last updated