-
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] Show remote es output error state on UI #172181
Conversation
Pinging @elastic/fleet (Team:Fleet) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
const latestHit = response.hits.hits[0]._source as any; | ||
return { | ||
state: latestHit.state, | ||
message: latestHit.message ?? '', |
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.
we might want to add the timestamp, to report the last time on the UI, in case the health reporting stopped and the state might be stale
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.
.../public/applications/fleet/sections/settings/components/edit_output_flyout/output_health.tsx
Outdated
Show resolved
Hide resolved
Couple of questions:
|
Is it possible that the same agent is checking in to multiple fleet servers? If so, then it's possible that two fleet servers start pinging the same remote ES. If they report different state to the data stream, we might see it as oscillating between healthy and degraded on the UI.
Yes, this would be nice, I was thinking about this. I'll add it. |
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 🚀
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
## Summary Closes #104986 Enable feature flags for `remoteESOutput` and `outputSecretsStorage`. The feature is ready when #172181 and elastic/fleet-server#3127 is merged. Output secret storage [issues](#157458) are closed, so I think the feature flag for that should be enabled too. cc @jillguyonnet
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! 🚀
Summary
Relates elastic/fleet-server#3116
Relates #104986
Reading latest output health state from
logs-fleet_server.output_health-default
data stream by output id, and displaying error state on UI - Edit Output flyout.Steps to verify:
remoteESOutput
remote_elasticsearch
output, can be a non-existent host for this testThe UI was suggested in the design doc: https://docs.google.com/document/d/19D0bX7oURf0yms4qemfqDyisw_IYB-OVw4oU-t4lf18/edit#bookmark=id.595r8l91kaq8
Notes/suggestions:
Added badges to output list:
Added healthy state UI to Edit output:
Checklist
Delete any items that are not applicable to this PR.