-
Notifications
You must be signed in to change notification settings - Fork 458
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
added output_health data stream to fleet_server #8605
Conversation
🌐 Coverage report
|
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.
these fields are not really serving any purpose (except @timestamp), added them out of convention
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.
LGTM!
Package fleet_server - 1.5.0 containing this change is available at https://epr.elastic.co/search?package=fleet_server |
Proposed commit message
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Start kibana locally and upload the new version of the package from
/build/packages
folder (or use elastic-package)The package installs successfully and the index template is created with the right fields and ilm policy.
The data streams are going to be populated by fleet-server: elastic/fleet-server#3127
The output health will be queried by kibana by output id (output keyword field) to show the state of remote es outputs on UI
Related issues
Relates elastic/fleet-server#3116
Screenshots