Operating

Observability Configuration

Enable observability and configure Cloud DSN and OTLP endpoints in Blnk.

This page lists the flags that control operational observability in Blnk Core. For how to think about logs, traces, and metrics, and for setup walkthroughs for Blnk Cloud and self-hosted export, see Monitoring in Blnk.

These settings are independent from queue monitoring, which exposes a separate HTTP port for queue inspection.

Observability flags

BLNK_ENABLE_OBSERVABILITY=false
BLNK_CLOUD_DSN=

{
  "enable_observability": false,
  "cloud_dsn": ""
}

For /metrics bearer authentication, see Server & security.

Exported logs have sensitive values redacted before they leave your instance.

Blnk Cloud DSN

Set the Blnk Cloud DSN when you export logs, traces, and metrics to Blnk Cloud monitoring:

• Environment: BLNK_CLOUD_DSN
• JSON: cloud_dsn

Requires enable_observability=true on the server and workers. See Quick setup: Blnk Cloud in Monitoring in Blnk.

OpenTelemetry endpoints

For self-hosted export, Blnk reads standard OpenTelemetry environment variables. Set them on both the server and worker. Observability must be enabled.

Blnk exports traces and metrics over OTLP HTTP (port 4318 in typical Jaeger or Collector setups, not gRPC port 4317). Set a separate endpoint per signal on both the server and worker. Observability must be enabled.

OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://jaeger:4318
OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=http://otel-collector:4318

These variables are environment-only. They are not set in blnk.json.

Metrics push runs on a 60-second interval. Prometheus-compatible metrics are also available at /metrics on the API port and worker monitoring port regardless of OTLP settings. See Connect to other tools in Monitoring in Blnk.

Logs are not exported through these endpoints. Collect process output with your log shipper, or set the Blnk Cloud DSN for managed log export.

Product telemetry

BLNK_ENABLE_TELEMETRY=false

{
  "enable_telemetry": false
}