Skip to main content
This feature is available in both Community Edition (open source) and Enterprise Edition.

​
Overview

All Formance Platform services emit distributed traces using the OpenTelemetry standard. Traces provide end-to-end visibility into request flows across services, helping you debug latency issues, understand service dependencies, and monitor platform behavior. Traces are sent to any backend that supports the OpenTelemetry protocol (OTLP), such as Jaeger, Grafana Tempo, Datadog, or any compatible collector.

​
Configuration

Traces are configured through the OpenTelemetry settings at the stack level. See Configure OpenTelemetry for the general setup. The following settings control trace collection:
SettingTypeDescription
opentelemetry.traces.dsnURIOpenTelemetry collector endpoint
opentelemetry.traces.resource-attributesMapAdditional resource attributes (e.g. key1=value1,key2=value2)

​
Example

apiVersion: formance.com/v1beta1
kind: Settings
metadata:
  name: stacks-otel-traces
spec:
  key: opentelemetry.traces.dsn
  stacks:
    - "formance-dev"
  value: grpc://opentelemetry-collector.formance-system.svc:4317?insecure=true

​
Stack identification

Every trace and span emitted by the platform includes a stack identifier following the format: 
organizationID-stackID
This allows you to filter and correlate traces across services for a specific stack in your observability backend.

​
Instrumented services

All data plane services emit traces:
  • Ledger
  • Payments
  • Orchestration (Flows)
  • Wallets
  • Reconciliation
  • Auth
  • Gateway
  • Webhooks