Fix Managed inputs nav path_prefix (404 on staging)#3603
Conversation
…-inputs The managed-inputs toc is built as part of opentelemetry://reference (path_prefix reference/opentelemetry), so its pages are served under reference/opentelemetry/managed-inputs. The standalone nav entry pointed at reference/managed-inputs, which had no built content and returned 404. Restore the opentelemetry segment (matching the previous motlp behavior) so the nav links resolve. Co-authored-by: Cursor <cursoragent@cursor.com>
📝 WalkthroughWalkthroughThis change updates a single navigation configuration entry in config/navigation.yml. The ChangesCompact metadata:
Related issues: None provided. Related PRs: None provided. Suggested labels: documentation, navigation Suggested reviewers: None specified. Poem:
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
config/navigation.yml (1)
478-479: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick winAlign the EDOT Collector path with the rest of the section
The
edot-collectorentry still publishes underreference/edot-collector, while the surrounding EDOT docs and existing link point toreference/opentelemetry/edot-collector. That mismatch will leave the Collector URL broken.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@config/navigation.yml` around lines 478 - 479, The EDOT Collector navigation entry is publishing under the wrong path and should match the rest of the EDOT section. Update the `edot-collector` item in the navigation configuration so the `path_prefix` aligns with the existing `reference/opentelemetry/edot-collector` route, using the `toc: elastic-agent://reference/edot-collector` entry as the locator.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@config/navigation.yml`:
- Around line 478-479: The EDOT Collector navigation entry is publishing under
the wrong path and should match the rest of the EDOT section. Update the
`edot-collector` item in the navigation configuration so the `path_prefix`
aligns with the existing `reference/opentelemetry/edot-collector` route, using
the `toc: elastic-agent://reference/edot-collector` entry as the locator.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 6d48d40f-b027-4c23-861c-79e03c5a4668
📒 Files selected for processing (1)
config/navigation.yml
Summary
Hotfix for the 404s on the Managed inputs pages after #3601. The
managed-inputstoc is built as part ofopentelemetry://reference(path_prefix: reference/opentelemetry), so its pages are served underreference/opentelemetry/managed-inputs/.... The standalone nav entry pointed atreference/managed-inputs, which has no built content, so every Managed inputs page 404'd.This restores the
opentelemetrysegment on thepath_prefix, matching the previousmotlpbehavior and the actual (working) content location.Effect
/reference/opentelemetry/managed-inputs/managed-otlp-endpoint.motlpredirects remain valid (/reference/opentelemetry/motlp/*→/reference/opentelemetry/managed-inputs/*).Related to elastic/docs-content#7155
Made with Cursor