Comments (11)
Pinging @elastic/agent (Team:Agent)
from elastic-agent.
@kevinlog What kind of health status info do you want reported? I saw you have policy response data that seems to indicate whether its running successfully. I suppose that only covers initialization, not if the endpoint becomes unhealthy later?
from elastic-agent.
@mostlyjason don't we already have another meta-issue regarding status reporting?
from elastic-agent.
What kind of health status info do you want reported? I saw you have policy response data that seems to indicate whether its running successfully. I suppose that only covers initialization, not if the endpoint becomes unhealthy later?
Endpoint will periodically update its Policy Response if there are meaningful events that change Endpoint's compliance with how the user configured it, so it could change during its lifecycle.
@ferullo could give more details on when this may happen.
from elastic-agent.
@kevinlog Do we need another health status reporting mechanism if we already have policy response status? What additional use cases do you require that are not offered by the policy response status?
from elastic-agent.
@mostlyjason sorry I missed this the first time.
Do we need another health status reporting mechanism if we already have policy response status? What additional use cases do you require that are not offered by the policy response status?
I don't believe Endpoint needs another mechanism, I just think that Fleet users may want additional insight if a subprocess isn't running correctly. Policy compliance for Endpoint is big. So if that's in a "Failed" state, it would be good to bubble that up to Agent so that it can be reported in the UI. Otherwise, all Agents are "Healthy".
I think we could do this in a generic way so that Integrations have the option to ship a "Success/Failure/Warning" status to let Fleet users know something isn't right. Then they could drill down further to individual Agents or solutions to investigate further.
Let me know if that makes sense
from elastic-agent.
++ sounds like a good idea to make policy responses a generic feature for all integrations. I haven't seen how it works currently, but conceptually it sounds good because it would provide a more structured error we could show on the agent details page, without the using having to dig through logs. It's also nice to have a uniform behavior if we don't have it already.
++ on having a failure response status put the agent into an unhealthy state so we keep our states consistent. Again, I'm not sure how that bubbles up but it sounds good conceptually.
As a general principal I think we don't expose processes to users directly, but the policy response could contain a aggregate of failures across all processes. We could show this aggregate info on the agent details page without exposing the underlying processes in the schema, which may result in a breaking change for users if we remove or change them in the future.
@jen-huang are you aligned on not exposing processes to users in the schema? How do you see this aligning with policy responses? Would it help to have a formal definition/design step for this issue?
from elastic-agent.
Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
from elastic-agent.
@pierrehilbert @nimarezainia Not sure if we have an appropriate meta issue that can supersede this one, so I am reopening for now but feel free to close and redirect.
from elastic-agent.
We have this one: https://github.com/elastic/ingest-dev/issues/1367
from elastic-agent.
Closing this as done.
cc @ycombinator
from elastic-agent.
Related Issues (20)
- [Flaky Test]: TestEndpointSecurityNonDefaultBasePath, TestEndpointSecurityUnprivileged – version conflict, document already exists HOT 7
- Error while enrolling unprivileged agent [mac] HOT 4
- Actionable error message when attempting to `inspect` an unprivileged Agent as a privileged user HOT 4
- Actionable error message when attempting to `enroll` an unprivileged Agent as a privileged user HOT 7
- Detect and fail early if user attempts to upgrade Fleet-managed Agent using the CLI HOT 4
- [Flaky Test]: TestRepeatedInstallUninstall – failed to set user elastic-agent-user password for service HOT 8
- `--insecure` flag should not be required during enroll/install because we have an `http` FLeet URL HOT 7
- Agent/beats gRPC over domain sockets/named pipes HOT 1
- Make `kubeletstatsreceiver` available in `otel` mode HOT 1
- Improve test proxy/mock fleet server to support further elastic-agent TLS tests HOT 3
- Fleet client configuration validation should take http status code into account HOT 5
- crash when logging empty line HOT 4
- [Windows] TestProxyURL fails with `access denied` error on `fleet.enc` HOT 8
- Can I customize the "agent.name" when sending data to ES instead of using hostname? HOT 1
- [Flaky Test]: TestRpmLogIngestFleetManaged/Monitoring_logs_are_shipped – failed to evaluate all symlinks HOT 3
- Integration tests framework creates more OGC VMs than needed HOT 2
- Extract creating of ESS deployment for integration tests in a separate mage target HOT 2
- Run Elastic Agent in `otel` mode as a service HOT 3
- [Integration Test Framework] Dump process list on first failure HOT 1
- [Flaky Test]: TestActionDispatcher/Dispatch_multiples_events_returns_one_error – Expected error HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from elastic-agent.