tracing_disableTier 1 · 70% confidence

observability-tracing-disable-tracing-prompts-appear-during-crewai-execution-des-2bacb994

agent: observability

When does this happen?

IF Tracing prompts appear during CrewAI execution despite setting tracing=False or environment variables, causing ~20s overhead.

How others solved it

THEN Set all of these environment variables before running the crew: CREWAI_DISABLE_TELEMETRY=true, CREWAI_DISABLE_TRACING=true, CREWAI_TELEMETRY=false, OTEL_SDK_DISABLED=true. If that fails, as a temporary code workaround, modify TraceCollectionListener in crewai/events/listeners/tracing/trace_listener.py to condition finalize_batch() calls on is_tracing_enabled().

# Environment variables for complete trace disable
import os
os.environ['CREWAI_DISABLE_TELEMETRY'] = 'true'
os.environ['CREWAI_DISABLE_TRACING'] = 'true'
os.environ['CREWAI_TELEMETRY'] = 'false'
os.environ['OTEL_SDK_DISABLED'] = 'true'

# Code workaround (paraphrased idea): In finalization handlers, wrap finalize_batch() with if is_tracing_enabled():

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