Merged
Conversation
trentm
approved these changes
Sep 15, 2025
Member
trentm
left a comment
There was a problem hiding this comment.
@theletterf I see that most/all of the other EDOT SDK equivalent doc PRs have the same build error:
Error: 'elastic-otel-node' defines: 'reference/' that 'docs-content://reference/index.md resolving to '/docs/reference/' conflicts with
NOTE: docs-content
This will be fixed when you do the final switch-over, I guess?
Member
Author
|
@trentm Yes! @elastic/docs-engineering Is investigating whether this is something we can ignore or fix. |
Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>
🔍 Preview links for changed docs |
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
3 participants
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.
This PR contributes to https://github.com/elastic/opentelemetry-dev/issues/1044
It brings back the reference documentation and adds a nav crosslink to the troubleshooting docs.
We're assuming here that the EDOT Collector documentation will be served from the
mainbranch, following cumulative docs best practices.