tracing_disablingTier 1 · 70% confidence

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

agent: observability

When does this happen?

IF Tracing prompts repeatedly appear during crew execution, adding ~20 seconds overhead, despite setting tracing=False or CREWAI_TRACING_ENABLED=false.

How others solved it

THEN Set the environment variables CREWAI_DISABLE_TELEMETRY=true, CREWAI_DISABLE_TRACING=true, and OTEL_SDK_DISABLED=true before running the crew. As a more permanent fix, modify the source file /crewai/events/listeners/tracing/trace_listener.py to guard finalize_batch() calls with a check for is_tracing_enabled().

os.environ['CREWAI_DISABLE_TELEMETRY'] = 'true'
os.environ['CREWAI_DISABLE_TRACING'] = 'true'
os.environ['OTEL_SDK_DISABLED'] = 'true'

Related patterns

otel_regression_span_processor

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

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%
integration_error

observability-integration-error-using-bedrockchat-with-langfuse-callbackhandler-re-4d0de297

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics