Skip to main content
ExecutionContext provides correlation IDs and traceability metadata for all TealTiger operations.

Overview

Every request should have an ExecutionContext that flows through:
  • TealEngine → TealGuard → TealCircuit → TealAudit
This enables:
  • Distributed tracing across services
  • Audit log correlation for investigations
  • Request attribution for cost and security analysis

Classes

Creating Contexts

Auto-generate correlation ID

Provide existing correlation ID

From HTTP headers

To HTTP headers

Context Propagation

Through TealEngine

Through TealGuard

Through TealAudit

Distributed Tracing

OpenTelemetry Integration

Multi-Service Correlation

Audit Log Correlation

Query by correlation ID

Investigation Workflow

Context Managers

Async Context Manager

Thread-Local Context

Environment Context

Best Practices

Always Create Context

Propagate Context

Extract from Headers

Type Hints

Performance

Context operations are designed to be fast:
  • Context creation: < 0.1ms (UUID generation)
  • Context propagation: < 0.5ms (object passing)
  • Header conversion: < 0.2ms (string serialization)