overview.md

Deployment

This section contains a general overview of deploying Tracetest in production. You can find platform-specific guides for:

• Docker
• Kubernetes

As shown in the diagram below, a typical production Tracetest deployment consists of Postgres, an OpenTelemetry Colletor and a trace data store. But, if you do not want to use a trace data store, you can rely entirely on OpenTelemetry Collector.

flowchart TD
    A(("Tracetest"))
    B[(Postgres)]
    C(OpenTelemetry Collector)
    D("Trace data store (optional)")


    A <--> |Tracetest stores test run data in Postgres| B
    C --> |OTel Collector sends traces to the trace data store| D
    D --> |Tracetest fetches traces to enrich e2e and integration tests| A

    classDef tracetest fill:#61175e,stroke:#61175e,stroke-width:4px,color:#ffffff;

    class A tracetest

Postgres stores all Tracetest-related data.

OpenTelemetry Collector ingests traces from your distributed system and forwards them to a trace data store.

A trace data store is used to store traces. Tracetest will fetch trace data from the trace data store when running tests.

Tracetest can be configured via a configuration file:

# tracetest.yaml

postgres:
  host: postgres
  user: postgres
  password: postgres
  port: 5432
  dbname: postgres
  params: sslmode=disable

Read more in the configuration docs.

Or, continue reading to see how to run Tracetest in production with Docker or Kubernetes.