Skip to content

docs: retire EDOT brand across all reference pages (9.5)#7434

Draft
alexandra5000 wants to merge 2 commits into
elastic:mainfrom
alexandra5000:docs/edot-rebrand
Draft

docs: retire EDOT brand across all reference pages (9.5)#7434
alexandra5000 wants to merge 2 commits into
elastic:mainfrom
alexandra5000:docs/edot-rebrand

Conversation

@alexandra5000

Copy link
Copy Markdown
Contributor

What does this PR do?

Renames all user-facing prose per the 9.5 product-naming decision (elastic/docs-content-internal#1242):

Old New
EDOT Collector Elastic Agent
EDOT SDKs / EDOT {Language} Elastic OTel SDKs / Elastic OTel {Language}
EDOT Cloud Forwarder Elastic Cloud Forwarder
EDOT (generic brand) {{edot}} → Elastic OpenTelemetry

Also updates docset.yml: edot sub → "Elastic OpenTelemetry".

119 files across troubleshoot/, solutions/observability/, reference/fleet/, reference/observability/, contribute-docs/, get-started/, manage-data/, and release-notes/.

Why is it important?

docs-content is the largest consumer of EDOT terminology and the hub for quickstarts, use cases, APM, logs, and troubleshooting guides. It needs to consistently reflect the new names before the 9.5 GA cutover.

Notes

Checklist

  • URL slugs and cross-repo links unchanged
  • applies_to frontmatter untouched
  • Code blocks with runtime output preserved
  • Old heading anchors explicitly preserved where headings were renamed
  • Tests (docs-only)

Renames all user-facing prose per the 9.5 product-naming decision
(elastic/docs-content-internal#1242):
- "EDOT Collector" → Elastic Agent
- "EDOT SDKs / EDOT {Language}" → Elastic OTel SDKs / Elastic OTel {Language}
- "EDOT Cloud Forwarder" → Elastic Cloud Forwarder
- Generic "EDOT" brand → {{edot}} (Elastic OpenTelemetry)

Also updates docset.yml: edot sub → "Elastic OpenTelemetry".

119 files updated across troubleshoot/, solutions/observability/,
reference/fleet/, reference/observability/, release-notes/ (historical
pre-9.5 entries preserved), and contribute-docs/.

All URL slugs, machine product-IDs, and cross-repo link paths are
unchanged. Code blocks with literal log output / SDK strings preserved.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

More links …

In total, 114 files changed.

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 4 warnings, 9 suggestions found

⚠️ Warnings (4): Fix when the suggestion improves clarity or correctness.
File Line Rule Message
solutions/observability/apm/apm-agents/central-configuration.md 29 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
solutions/observability/apm/opentelemetry/create-apm-agent-key-for-edot-sdks.md 26 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
solutions/observability/apm/opentelemetry/upstream-opentelemetry-collectors-language-sdks.md 24 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'vs'.
troubleshoot/ingest/opentelemetry/edot-sdks/android/index.md 28 Elastic.PluralAbbreviations Don't use apostrophes when making abbreviations plural. Use 'SDK' instead of ''s'.
💡 Suggestions (9): Optional style improvements. Apply when helpful.
File Line Rule Message
troubleshoot/ingest/opentelemetry/contact-support.md 18 Elastic.Wordiness Consider using 'sometimes' instead of 'In some cases'.
troubleshoot/ingest/opentelemetry/contact-support.md 18 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/contact-support.md 18 Elastic.WordChoice Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-collector/collector-not-starting.md 23 Elastic.WordChoice Consider using 'open' instead of 'launch', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-collector/collector-oomkilled.md 18 Elastic.WordChoice Consider using 'stop, exit' instead of 'terminate', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-collector/index.md 48 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-sdks/dotnet/index.md 336 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-sdks/index.md 54 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/ingest/opentelemetry/edot-sdks/index.md 59 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

Update the Mermaid flowchart subgraph label from "EDOT Collector (gateway)"
to "Elastic Agent (gateway)" to match the 9.5 product rebrand.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant