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
[libbeat/management]: support filebeat inputs to report their status to elastic-agent #39209
base: main
Are you sure you want to change the base?
[libbeat/management]: support filebeat inputs to report their status to elastic-agent #39209
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
💔 Build Failed
Expand to view the summary
Build stats
Pipeline error
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
149a0c5
to
c3ef49b
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
…ing multiple streams
c3ef49b
to
c6294b7
Compare
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
@andrewkroh @cmacknz @belimawr there are some rough edges (checking if the issue I spotted is actually an issue with elastic-agent-client, making the integration test use the integration stack and not the one I spawned from elastic-package) but the logic is pretty much there |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Proposed commit message
This PR introduces the following:
Healthy
this is immediately the status of the StatusUnit. This allows the existing runner allocation/deallocation logic to properly propagate any given status and highlight that something is changing, e.g. when a unit is modified the propagated status isconfiguring
which is what we want.Running
: everything is happy, no error or warning produced during the operation of an inputFailed
: when the input encountered an error that it can't continue fromDegraded
: when the input encountered something abnormal but, due to lack of a better expression, it hasn't given up yet 😄 CEL does that a lot, it denies to say bb.Configuring
,Stopping
,Stopped
,Starting
: These statuses are most suitable to be used by the input allocation/deallocation code and not directly from inside the input, as the former can and should override the status of the whole input.Noteworthy code changes:
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
N/A
Screenshots
N/A
Logs