docs: add the unified llmops tracing switch

[Ill-donut]

The three-language environment reference now documents OPS_TRACE_UNIFIED_ENABLED, default false, alongside the existing trace delivery settings. It explains the common workflow/node structure for LangSmith and Arize/Phoenix, points Compose users to docker/envs/core-services/shared.env, and makes the parent-context TTL validation conditional on enabling the switch.

Verified at Dify 1.17.0 (09a855dcef24c0edc7431c46c0cfaa494481daf5) and 1.17.1 (8387590ace4a094de812b7847fc6a4c3a27cd52b):

• docker/envs/core-services/shared.env.example and api/configs/feature/__init__.py: exposed boolean switch, default false; enabling it requires TTL to cover retries × delay.
• api/core/ops/ops_trace_manager.py and api/core/ops/unified_trace/{registry,trace_builder,parent_context}.py: provider selection, shared trace structure and per-app tracing prerequisites.
• The LangSmith and Arize/Phoenix unified_trace.py adapters consume the common builder. Other providers keep their existing implementation.
• docker/docker-compose.yaml: shared env file reaches API and worker services; .env overrides it. No Helm configuration was copied.

Validation: the complete environment verifier scans both env-example sources and deployment Compose files and passes for en/zh/ja. Isolated execution of the pinned source validator passes 6 boundary probes, and dispatch selection passes 12 on/off and provider probes. Independent final English, Chinese and Japanese reviews have no marks in the changed units. Structural parity and internal links/anchors/navigation pass; git diff --check passes. English/Chinese format findings are zero; the Japanese page retains four pre-existing whole-page findings with zero new violations. No checker or writing rule changed. These source probes do not claim live provider delivery or cluster acceptance.

Only this missing switch and its necessary neighboring explanation are changed. The other advanced settings are already documented. ARCHIVE_STORAGE_ADDRESS_STYLE is absent from CE 1.17.1 and is not included. Same-file PR #1057 changes Huawei OBS, not this section; its branch is untouched.

Proposed after main review and merge:

• backport-to-release/1.17.0: the switch, provider registry, validator and Compose entry are present at the released tag.
• backport-to-release/1.17.1: the same configuration contract is present.

Earlier retained versions lack this switch. No backport label or automatic document merge is requested. The full-page reader test is not applicable to this partial reference edit.

Backport preflight: local cherry-pick simulations on every proposed target applied cleanly, and resulting file-content probes passed. This does not represent an actual remote backport.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
dify-ce-cloud-docs	🟢 Ready	View Preview	Sep 30, 2026, 9:12 AM

💡 Tip: Enable Automations to automatically generate PRs for you.