-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Event.dataset is set differently for KSM between beats and Elastic Agent #36227
Comments
This description is not totally correct, we see the same behavior using metricbeat: elastic/integrations#7144 (comment). |
One thing also to mention here is that in elastic-agent: state_pod: https://github.com/elastic/integrations/blob/main/packages/kubernetes/data_stream/state_pod/sample_event.json#L105 So we need to understand why this was not picked in our tests |
@constanca-m I think what you indicate is a different issue compared to what @gizas described:
In any case we need to figure out which values are set and why. Also check which one is the correct one to use. And last but not least to document our findings. |
In order to be sure we can test only with kube-state-metrics datastream enabled. Also my tests with elastic-package Only if I delete the sample_event.json file are failing :)
|
Which version of |
@zmoog you were correct, I was testing in an old branch where Now I pulled latest one,
and when I change "event": {
"dataset": "kubernetes.node", (it was "dataset": "kubernetes.state_node",) test correctly fails PACKAGE="kubernetes" elastic-package test -vvv static
2023/08/17 17:06:52 DEBUG Enable verbose logging
2023/08/17 17:06:53 INFO New version is available - v0.85.0. Download from: https://github.com/elastic/elastic-package/releases/tag/v0.85.0
Run static tests for the package
--- Test results for package: kubernetes - START ---
FAILURE DETAILS:
kubernetes/state_node Verify sample_event.json:
[0] field "event.dataset" should have value "kubernetes.state_node", it has "kubernetes.node" |
Hi! We're labeling this issue as |
Investigate why event.dataset is set differently for kube-state-metrics metricsets between Elastic agent and Beats.
See below images for:
Beats:
For Elastic Agent:
So for the same kube-state-metrics node metricset we can see that event.dataset is state_node in Elastic Agent vs node in Beats.
We should investigate where this change came from and see if we need to backport any changes in beats code.
Related discussion:
elastic/integrations#7144 (comment)
The text was updated successfully, but these errors were encountered: