Skip to content

docs: replace vague Collector diagram with Mermaid flowchart (#9494)#9702

Open
LoveChauhan-18 wants to merge 1 commit intoopen-telemetry:mainfrom
LoveChauhan-18:fix/collector-diagram-9494
Open

docs: replace vague Collector diagram with Mermaid flowchart (#9494)#9702
LoveChauhan-18 wants to merge 1 commit intoopen-telemetry:mainfrom
LoveChauhan-18:fix/collector-diagram-9494

Conversation

@LoveChauhan-18
Copy link
Copy Markdown

@LoveChauhan-18 LoveChauhan-18 commented Apr 20, 2026

  • I have read and followed the Contributing docs, especially the "First-time contributing?" section.
  • This PR has content that I did not fully write myself.
  • I have the experience and knowledge necessary to understand, review, and validate all content in this PR.1

Resolves #9494 by replacing the vague static SVG diagram in the Collector introduction with a Mermaid flowchart that explicitly models the two deployment options discussed in the text:

  1. Option 1: Direct Export - App sends directly to backends (for dev/simple setups)
  2. Option 2: Via Collector - App -> OTel Collector (Receivers | Processors | Exporters) -> Backends (recommended for production)

This clarifies the app-to-backend flow and completely replaces the obsolete otel-collector.svg asset across all three locales (en, ja, zh).

Footnotes

  1. Yes, I can answer maintainer questions about the content of this PR, without using AI.

@LoveChauhan-18 LoveChauhan-18 requested a review from a team as a code owner April 20, 2026 18:37
@otelbot-docs otelbot-docs Bot requested review from a team April 20, 2026 18:37
@otelbot-docs otelbot-docs Bot requested review from songy23 and removed request for a team April 20, 2026 18:37
@otelbot-docs otelbot-docs Bot added the missing:docs-approval Co-owning SIG has provided approval, PR needs approval from docs maintainer label Apr 20, 2026
@otelbot-docs otelbot-docs Bot added the missing:sig-approval Co-owning SIG didn't provide an approval label Apr 20, 2026
…lemetry#9494)

Resolves open-telemetry#9494 by replacing the static Collector SVG with a dynamic
Mermaid diagram that explicitly models both deployment options mentioned
in the text:
1. Direct Export (Dev/Simple)
2. Via Collector (Production)

This clarifies the app-to-backend flow and eliminates the confusing SVG.
@LoveChauhan-18 LoveChauhan-18 force-pushed the fix/collector-diagram-9494 branch from b7d4daf to 9b2526e Compare April 20, 2026 18:48
@otelbot-docs otelbot-docs Bot requested a review from a team April 20, 2026 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lang:ja lang:zh missing:docs-approval Co-owning SIG has provided approval, PR needs approval from docs maintainer missing:sig-approval Co-owning SIG didn't provide an approval sig:collector

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[Doc] The collector diagram is quite vague.

1 participant