-
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] Add periodic logs for agent status #140014
Comments
Pinging @elastic/fleet (Team:Fleet) |
We can probably safely backport this as well to 8.5.x. |
@elastic/kibana-core I tried to look at this but I did not find an easy way to do so, it's possible to know what log level is currently enabled for a plugin? |
No, we currently don't have an equivalent to log4j's Having it would make sense though, and shouldn't be too complex to implement in theory |
I created #144002. Will try to take a preliminary look this week |
@nchaulet We should test how necessary this optimization would be to get this out. For instance, how fast would this query be on an index of 250k agent documents? My guess is it's actually quite fast and very easily cacheable. |
@joshdover Looking at the trace for agent status (it's the same ES queries here) for 300k agents this seems pretty fast and maybe we do not have to do that optimization. |
FWIW the PR is ready: #144033, so you may be able to use it very soon if you need to. |
Validation steps for QA:
|
Hi @nchaulet, We have re-validated this issue on the latest 8.6.0 SNAPSHOT Kibana Staging environment Build details:
Observations:
Further, CC: @kpollich we have few queries:
We have observed the
Please let us know if we are missing anything. Thanks! |
@nchaulet could you take a look at the above? Seems like we're not getting the |
Hi @prachigupta-qasource looks like I should have given more info on how to test this/what is the expected behavior That task add new Kibana logs (not agent/fleet server), you should see in your Kibana logs somethings like this
Does it make sense to you? |
Hi @nchaulet, We have re-validated this issue on the latest 8.6.0 SNASPSHOT Kibana Staging environment and found the below observations. Observations:
Screenshots: Build details:
Query
So @kpollich, we wanted to confirm if new Please let us know if we are missing anything. Thanks! |
Hi @prachigupta-qasource The debug logs should change to 5 minute when settings the kibana plugin fleet log level not the agent log level. Let me know if it's clearer to you. |
Hi @nchaulet, Thank you for the feedback and looking into our queries. We have added xpack Observations: What's working:
What's not working:
Screenshots: Build Details:
Please let us know if we are missing anything. Thanks! |
Hi @nchaulet, We have created below 02 test cases for this feature under our Fleet Test Suite:
Please review the test cases and let us know if we are missing anything. Thanks! |
Hi @nchaulet, We have updated our details observations related to collection of Further, as per above shared observation, we are So, Could you please look into it, so that we can continue on above testing. Please let me know if we are missing anything. Thanks! |
Hi @nchaulet, We have re-validated this ticket after fixes on #148635 on the latest 8.7.0 SNAPSHOT Kibana Staging environment and found the below observations. Observations:
Screenshot: Build details:
Hence, marking this ticket as QA: Validated. Thanks! |
It'd be helpful in troubleshooting cases to have some amount of logging around the status of the Fleet. We currently have no live visibility around this without requesting information from the end-user but we could make this available in the logs.
We can likely re-use the same code path we use to collect this for product telemetry: https://github.com/elastic/kibana/blob/94b1267c389c6cf0451781ad2194c52c4075510c/x-pack/plugins/fleet/server/collectors/agent_collectors.ts/#L22
I'd propose we:
One thing to consider when implementing this would be that it'd be best to minimize queries on this index if possible. For instance, it'd be better to not run the query make the
log.debug
call at all if debug logging is disabled.The text was updated successfully, but these errors were encountered: