Skip to content

Conversation

ChrsMark
Copy link
Member

@ChrsMark ChrsMark commented Sep 9, 2025

What does this PR do?

Adds the k8seventsreceiver otel component.

Why is it important?

We want to switch from using the k8sobjectsreceiver to using the k8seventsreceiver as described at #9791.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • 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/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

TBA

@ChrsMark ChrsMark requested a review from a team as a code owner September 9, 2025 07:53
Copy link
Contributor

mergify bot commented Sep 9, 2025

This pull request does not have a backport label. Could you fix it @ChrsMark? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Sep 9, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

Copy link
Contributor

mergify bot commented Sep 12, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b add_k8sevents_receiver upstream/add_k8sevents_receiver
git merge upstream/main
git push upstream add_k8sevents_receiver

@ChrsMark
Copy link
Member Author

blocked by #9858

@ChrsMark ChrsMark force-pushed the add_k8sevents_receiver branch from 313477b to 748e99f Compare September 22, 2025 08:49
@ChrsMark ChrsMark requested a review from a team September 22, 2025 08:55
@ChrsMark ChrsMark enabled auto-merge (squash) September 22, 2025 09:50
@ChrsMark
Copy link
Member Author

Screenshot 2025-09-22 at 2 12 33 PM

Testing this locally and the data_stream.dataset field is correctly set to k8seventsreceiver.otel.

@ChrsMark
Copy link
Member Author

K8s Events related panels can be re-created using the data that the k8sevents receiver ships:

Screenshot 2025-09-22 at 2 30 07 PM Screenshot 2025-09-22 at 2 47 46 PM
  • Note that I could not use body.text in the Events table for now, but I will investigate this further.

Copy link

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @ChrsMark

@ChrsMark ChrsMark merged commit 710c49f into elastic:main Sep 22, 2025
24 of 26 checks passed
intxgo pushed a commit to intxgo/elastic-agent that referenced this pull request Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants