-
Notifications
You must be signed in to change notification settings - Fork 495
[k8s otel] Use k8seventsreceiver data for K8s Events panels #15454
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
318ac95
to
dceabcd
Compare
dceabcd
to
4d21b06
Compare
4d21b06
to
205129f
Compare
205129f
to
1c04dd0
Compare
@@ -0,0 +1,3 @@ | |||
errors: |
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.
nit: just write a comment for which error this exclusion was added
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.
Done: f177c2e
Thank's!
Signed-off-by: ChrsMark <[email protected]>
1c04dd0
to
f177c2e
Compare
💚 Build Succeeded
History
cc @ChrsMark |
|
Package kubernetes_otel - 1.2.0 containing this change is available at https://epr.elastic.co/package/kubernetes_otel/1.2.0/ |
Proposed commit message
This PR updates the K8s Events related visualisations in order to use the data coming from the
k8sevents
receiver directly instead of handling the raw events thatk8sobjects
receiver collects.This will fix the issue with the
body.structured.*
fields being non-searchable without an ES mapping being provided. See elastic/elastic-agent#9791 and #15127 for more information.Checklist
changelog.yml
file.How to test this PR locally
Using
elastic-package
or by installing to a Serverless project:Related issues
Screenshots
Local Stack using
elastic-package
:Serverless project:

Visualisations: