-
Notifications
You must be signed in to change notification settings - Fork 198
Document Kubernetes objects receiver (k8sobjectsreceiver)
#10696
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 |
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.
Just a couple nits from my side!
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
Hey @ChrsMark I applied your comments. Please approve if it looks ok to you now 🙂 |
|
@Mergifyio backport 9.1 9.2 |
✅ Backports have been created
|
* Document k8sobjects receiver * Apply comments * Apply comments (cherry picked from commit a3f3f0a)
* Document k8sobjects receiver * Apply comments * Apply comments (cherry picked from commit a3f3f0a)
…11019) * Document k8sobjects receiver * Apply comments * Apply comments (cherry picked from commit a3f3f0a) Co-authored-by: Aleksandra Spilkowska <[email protected]>
…11020) * Document k8sobjects receiver * Apply comments * Apply comments (cherry picked from commit a3f3f0a) Co-authored-by: Aleksandra Spilkowska <[email protected]>
What does this PR do?
This PR introduces a new documentation page for the k8sobjects receiver, a core component of the EDOT Collector.
The page covers:
Overview of the receiver’s purpose and how it integrates with Elastic Observability
Configuration examples
Caveats and limitations
Why is it important?
The
k8sobjectsreceiveris included in the default EDOT Collector distribution, but was not yet documented.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
No
How to test this PR locally
Follow the Contribute locally guide.
Related issues
Closes #1028