Trace Ingestion

Tracetest allows you to connect your Tracing Backend to unlock the full potential of trace-based testing. Tracetest supports two types of tracing backend integrations.

OTLP Ingest Endpoint

When not using a tracing backend, the OpenTelemetry Collector, or using a tracing backend integration that does not support a native connection, you'll use the Tracetest OTLP ingest endpoint.

Configure Tracetest Agent:

• Tracetest Agent exposes an OTLP endpoint that listens for trace data on ports 4317 (gRPC) and 4318 (HTTP).
• Tracetest Cloud Agent exposes an OTLP endpoint that listens for trace data on TLS port 443 (both HTTP and gRPC).

Configure trace ingestion:

• OTLP Ingestion Endpoint is used to ingest OpenTelemetry traces.

Supported OTLP Ingest Tracing Backends

Currently, Tracetest integrates with the following OTLP tracing backends. Click on the respective tracing backend to view configuration examples:

• OpenTelemetry Collector
• Azure App Insights
• Dash0
• Datadog
• Dynatrace
• Instana
• Lightstep
• New Relic
• SigNoz

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.

Supported Native Tracing Backends

Currently, Tracetest supports the following tracing backends. Click on the respective tracing backend to view configuration examples:

• AWS X-Ray
• Azure App Insights
• Elastic APM
• Grafana Tempo
• Jaeger
• OpenSearch
• SignalFX
• Sumo Logic

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.