Connecting to Tracing Backends

Tracetest supports two types of tracing backend integrations.

Native Connection (Polling)

When using a tracing backend integration that supports the native connection, Tracetest will pull telemetry data directly from your tracing backend for every test run.

OTLP Ingest Endpoint

When using a tracing backend integration that does not support a native connection, or no tracing backend at all, you'll resort to using the Tracetest OTLP ingest endpoint. Tracetest Agent exposes an OTLP endpoint that listens for trace data on ports 4317 (gRPC) and 4318 (HTTP). As does Tracetest Cloud Agent, but uses the same TLS port 443 for OTLP ingestion.

Supported Tracing Backends

Currently, Tracetest supports the following data stores. Click on the respective data store to view configuration examples:

• AWS X-Ray
• Azure App Insights
• Datadog
• Dynatrace
• Elastic APM
• Grafana Tempo
• Honeycomb
• Instana
• Jaeger
• Lightstep
• New Relic
• OpenSearch
• OpenTelemetry Collector
• SignalFX
• SigNoz
• Sumo Logic

Using Tracetest without a Tracing Backend (OTLP ingest endpoint)

Another option is to send traces directly to Tracetest using the OpenTelemetry Collector. And, you don't have to change your existing pipelines to do so.

View configuration for OpenTelemetry Collector for more details.

Tracing Backend Configuration Examples

• View the examples folder of the Tracetest GitHub repo.
• Follow the Recipes for guided walkthroughs of sample use cases.

We will be adding new data stores over the next couple of months - let us know any additional data stores you would like to see us support.