-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Fleet] Support dataset with multiple level like system.process.summary #99852
[Fleet] Support dataset with multiple level like system.process.summary #99852
Conversation
Pinging @elastic/fleet (Team:Fleet) |
Should we backport this to 7.13? |
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.
- Yes, this is a good 7.13 candidate.
- Would this be fixed if Attempt to fix process summary name integrations#778 also exported
path: process_summary
? (It's still good to have a fallback in Kibana, aka this PR)
Actually the package registry populate the Just did a quick check against the snapshot registry and the dataset we computed before and the path match for all packages expect
|
💚 Build SucceededMetrics [docs]Unknown metric groupsReferences to deprecated APIs
History
To update your PR or re-run it, just comment with: cc @nchaulet |
/run-fleet-e2e-tests |
Summary
Resolve #92636
Currently when a datastream use a dataset with multiple dots we are not using the correct agent template.
We where looking to find the dastream by splitting the dataset name on
.
instead of using the datastreampath
propertyThat PR fix that.
How to test
You can try that PR elastic/integrations#778 run the package registry and you will get the correct
agent template for
system.process.summary