Configuration

There are several configuration options with Tracetest:

• Server configuration to set database connection information needed to connect to required PostgreSQL instance.
• Provisioning configuration to 'preload' the Tracetest server with resources when first running the Tracetest server.

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
• Honeycomb

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

Configuring the Server

Tracetest has a configuration file to contain the minimal information needed to start the Tracetest server. See more at Tracetest Server Configuration.

You can also provision the server when it first starts, configuring most aspects of your Tracetest server environment. This is useful in a CI/CD environment to preload and configure the server. See more at Provisioning a Tracetest Server.

Many of the server configuration settings can be set individually in the UI or via the CLI. See:

• Trace Polling
• Demo Applications
• Analytics