OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

Distributed Tracing

ContractSpec uses OpenTelemetry (OTel) for distributed tracing. This guide explains how to configure exporters and collectors.

Configuration

Configure the OTel SDK via environment variables:

OTEL_SERVICE_NAME=my-service
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
OTEL_TRACES_SAMPLER=parentbased_traceidratio
OTEL_TRACES_SAMPLER_ARG=0.1

Exporters

By default, the OTLP exporter is used. You can point it to:

  • Jaeger

  • Tempo (Grafana)

  • Honeycomb

  • Datadog (via OTel Collector)

OSS docsoperateStart with OSS. Adopt Studio when you want the operating layer.
Previous

Observability and cost evidence

Emit traces, metrics, structured logs, and durable cost/usage evidence through one Instrumentation facade, SignalSpec contracts, and the append-log evidence bus.

Next

Integrations overview

Understand the binding model for external services, providers, and tenant-owned connections.

Why ContractSpec

Keep educational and comparison content reachable without letting it define the primary OSS learning path.

ManifestoContract-first APISpec-driven development