-
Notifications
You must be signed in to change notification settings - Fork 204
Add documentation page for the EDOT Collector APM config connector #11344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔍 Preview links for changed docs |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
theletterf
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! We might want to get @hegerchr to also have a look.
|
@Mergifyio backport 9.1 9.2 |
✅ Backports have been created
|
…11344) (#11462) * Add apmconfigextension docs * Update for clarity and detail * Alphabetize components in toc * Apply comments (cherry picked from commit 0d53bef) Co-authored-by: Aleksandra Spilkowska <[email protected]>
…11344) (#11461) * Add apmconfigextension docs * Update for clarity and detail * Alphabetize components in toc * Apply comments (cherry picked from commit 0d53bef) Co-authored-by: Aleksandra Spilkowska <[email protected]>
What does this PR do?
This PR adds a new documentation page for the APM config connector (
apmconfigextension), a core Elastic-provided component included in the EDOT Collector distribution.This documentation is based on the upstream Elastic component located here:
https://github.com/elastic/opentelemetry-collector-components/tree/main/extension/apmconfigextension
Why is it important?
The APM config connector is the core mechanism enabling EDOT SDK central configuration using OpAMP. It currently lacks standalone documentation in the Elastic docs.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in./changelog/fragmentsusing the changelog tool[ ] I have added an integration test or an E2E testDisruptive User Impact
This PR has no disruptive user impact.
How to test this PR locally
Follow the Contribute locally guide.
Related issues
GenAI disclosure
I used Claude 4.5 Sonnet to modify my first draft to keep the style and conventions used in other components docs. I then edited the output again for minor style issues and accuracy.