tracing_telemetryTier 1 · 70% confidence

observability-tracing-telemetry-tracing-prompts-appear-and-add-20s-overhead-per-cr-b0cfb346

agent: observability

When does this happen?

IF Tracing prompts appear and add ~20s overhead per crew run despite setting CREWAI_DISABLE_TRACING=true, CREWAI_DISABLE_TELEMETRY=true, OTEL_SDK_DISABLED=true, and other environment variables.

How others solved it

THEN In TraceCollectionListener, guard the calls to finalize_batch() in the handlers for CrewKickoffCompletedEvent and CrewKickoffFailedEvent with a check like `if is_tracing_enabled(): self.finalize_batch()`. This ensures batch finalization only occurs when tracing is explicitly enabled.

def handle_kickoff_completed(self, event):
    if is_tracing_enabled():
        self.finalize_batch(event.session_id)

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics