Configuration

To enable Tracetest to run end-to-end tests against trace data, you need to configure Tracetest to access your app. Tracetest is designed to work with tracing backends, or to ingest trace data via an OTLP ingest endpoint.

Enable Tracetest to Access Your Application

There are two configuration options for triggering tests and ingesting trace data into Tracetest:

• Tracetest Agent configuration (private access): You run an agent locally in your environment, as a process, or in Docker/Kubernetes as a container. Prefferred option if you are using a VPC, firewall, etc.
• Tracetest Cloud Agent configuration (public access): We run an agent in your Tracetest account with publicly accesible endpoints. You manage nothing. Prefferred option if you are using serverless architectures.

Connecting Tracetest to Tracing Backends

Tracetest supports two types of tracing backend integrations:

• Native connection (polling)
• OTLP ingest endpoint

Want to see your options?

View the list of supported tracing backends, here.

Access and 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.