Rename Envoy AI Gateway to Agent Router in the docs - #14082
Merged
Merged
Conversation
Envoy AI Gateway became Agent Router on 2026-09-10 and moved to the Agentic AI Foundation. Only the product name changed: Agent Router kept its API group, CLI, images and emitted telemetry. Update the operator doc, menu, marketplace entry and OTLP receiver doc to the new name, and keep the ENVOY_AI_GATEWAY layer, the job_name=envoy-ai-gateway routing tag, the envoy-ai-gateway rule files, the meter_envoy_ai_gw_ metric names and the doc URL unchanged so existing deployments, stored data and links keep working.
wu-sheng
added
the
documentation
There was a problem hiding this comment.
🟢 Approval recommended
The only remaining finding is a minor documentation nit that does not block approval.
Pull request overview
Updates documentation and Javadoc to rename Envoy AI Gateway to Agent Router while preserving compatibility-sensitive identifiers.
Changes:
- Renames product references, links, navigation, and marketplace content.
- Documents retained API, routing, rule, metric, and layer names.
- Records the rename in the changelog.
File summaries
| File | Description |
|---|---|
oap-server/server-core/src/main/java/org/apache/skywalking/oap/server/core/analysis/Layer.java |
Updates ENVOY_AI_GATEWAY documentation. |
docs/menu.yml |
Renames the navigation entry. |
docs/en/setup/backend/opentelemetry-receiver.md |
Updates the routing example. |
docs/en/setup/backend/marketplace.md |
Updates the marketplace reference. |
docs/en/setup/backend/backend-envoy-ai-gateway-monitoring.md |
Renames and clarifies the monitoring guide. |
docs/en/changes/changes.md |
Records the documentation rename. |
Review details
Suppressed comments (1)
docs/en/setup/backend/backend-envoy-ai-gateway-monitoring.md:17
- The compatibility section lists the API group and
aigwCLI but omits thedocker.io/envoyproxy/ai-gateway-*image names, which also remain unchanged according to the rename scope. Please include that image pattern here so operators do not infer that they must switch image repositories or tags.
Agent Router kept the names you deploy (the `aigateway.envoyproxy.io` API group, the `aigw` CLI) and emits the same
- Files reviewed: 6/6 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
wankai123
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rename Envoy AI Gateway to Agent Router in the docs
Envoy AI Gateway became Agent Router on 2026-09-10 and moved to the Agentic AI Foundation. Per the announcement, only the product name changed. The
aigateway.envoyproxy.ioAPI group, theaigwCLI, thedocker.io/envoyproxy/ai-gateway-*images and the emittedgen_ai.*/mcp.*metrics are unchanged, so our MAL/LAL rules still match.Renamed in prose:
Layer.ENVOY_AI_GATEWAY.Kept on purpose, because renaming would break existing gateway deployments, stored data, dashboards, alarm rules and links:
ENVOY_AI_GATEWAYlayer and thejob_name=envoy-ai-gatewayrouting tag that operators set on their gateways.otel-rules/envoy-ai-gateway/*andlal/envoy-ai-gateway.yamlrule files, and themeter_envoy_ai_gw_*metric names.SWIP-10, SWIP-11 and the released changelogs are frozen and not touched. The UI layer name in Horizon UI will be renamed in a separate PR there.
CHANGESlog.