_Docs/
Get StartedModulesPlatformDeployCookbookChangelogReference
_Deploy
  • Deployment Overview
    • Overview
    • Requirements
    • Demo
      • All-in-one Demo Chart
    • Installation
      • Operator Setup
      • Control Plane SetupEE
    • Infrastructure Services
      • PostgreSQL
      • Message Broker
      • Temporal
    • Module Configuration
      • Stack Configuration
      • Gateway Module
      • Ledger Module
      • Payments Module
      • Auth ModuleEE
      • Orchestration ModuleEE
      • Reconciliation ModuleEE
      • Wallets ModuleEE
      • Webhooks ModuleEE
    • Configuration Reference
      • Operator settings reference
      • API Reference
    • Backups management
    • Troubleshooting
    • Configure OpenTelemetry
    • Traces
    • Metrics
    • Upgrade from the operator
    • Database update
  1. Manage
  3. Observability
  5. Traces
Deploy

Traces

This page requires self-hosted edition.
Deployment

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.

opentelemetry.traces.dsn
example: grpc://otel-collector:4317?insecure=truedefault: noneuri

OTLP endpoint URI used to send distributed traces; enables OpenTelemetry tracing for all services when set.

This setting can be configured on Formance Cloud deployments by contacting your Formance Cloud support team.
opentelemetry.traces.resource-attributes
default: none
This setting can be configured on Formance Cloud deployments by contacting your Formance Cloud support team.

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
Configure OpenTelemetryMetrics
On This Page
  • Overview
  • Configuration
  • Stack identification
  • Instrumented services