Correlation IDs

Correlation Key Hierarchy

Finding All Signals for One Execution

# Logs in Loki — all log entries for one execution
{executionId="exec-abc-123"}

# Logs for one specific node within that execution
{executionId="exec-abc-123", nodeId="node-approval-1"}

# Traces in Tempo — find the execution trace
{ resource.executionId = "exec-abc-123" }

# Metrics in Prometheus — query for this execution's node durations
node_execution_duration_ms{executionId="exec-abc-123"}

TraceId in Log Entries

// Every INodeLogger entry includes the current OTel TraceId:
// In Loki, click a log entry → copy the traceId field
// Open Tempo → search by that traceId → see the full distributed trace

// Log entry example in Loki:
{
  "timestamp"  : "2026-05-25T09:00:12Z",
  "level"      : "Information",
  "message"    : "Approval task submitted",
  "nodeId"     : "node-approval-1",
  "executionId": "exec-abc-123",
  "tenantId"   : "tenant-001",
  "traceId"    : "3d7f6c9a1b2e4f8..."  // ← link to Tempo
}

Grafana Exemplars

When BizFirst Observe is configured with exemplar support, Prometheus metrics link directly to Tempo traces via the TraceId. Clicking a spike in the node duration histogram in Grafana opens the corresponding trace in Tempo — no manual correlation needed.