Configuration Overview

There is one way you can set configuration options in Tracetest. By using a configuration file, commonly known as the tracetest.config.yaml file.

When using Docker, ensure that the configuration file is mounted to /app/config.yaml within the Tracetest Docker container.

Supported Trace Data Stores

Tracetest is designed to work with different trace data stores. To enable Tracetest to run end-to-end tests against trace data, you need to configure Tracetest to access trace data.

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

• Jaeger
• OpenSearch
• Elastic
• SignalFX
• Grafana Tempo
• Lightstep
• New Relic
• AWS X-Ray
• Datadog

Using Tracetest without a Trace Data Store

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 the configuration for OpenTelemetry Collector for more details.

Trace Data Store Configuration Examples

Examples of configuring Tracetest to access different data stores can be found in the examples folder of the Tracetest GitHub repo. Check out 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.