-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Inconsistent with high frequency]: Agent logging level not updated #25385
Comments
Pinging @elastic/agent (Team:Agent) |
@manishgupta-qasource Please review |
Reviewed & Assigend to @EricDavisX |
I have seen in some usage it can take up to 15 seconds for the setting to be in place on the host Agent (meaning you can refresh the browser multiple times before it shows as being updated). If you can confirm any behavior that takes longer we should investigate. @dikshachauhan-qasource can you time it and re-post back please? |
Hi @EricDavisX , Specially on windows its not reflecting at all. For rest it gets updated after 2-3 mins after refreshing and updating logging level several times. |
Hi @EricDavisX UPDATE: Today while performing regression on cloud-prod environment, we observed this issue occurring here too. Build details: Thanks |
@dikshachauhan-qasource with recent stability improvements it would be good to know if this was still reproducible in latest 7.13 snapshot or 8.0 snapshot code - can you re-test please? I'm logging a separate ticket for Agent continuing to go off-line/on-line which may relate to this, but we'll see. |
Hi @EricDavisX While performing testing today on 7.13BC4 build, we have observed this issue is now no more reproducible. We are now able to update Agent logging level and updated level is reflected at all places with 2 mins max. Build details:
Hence we are closing this issue. Thanks |
Kibana version:
7.13 BC3 Kibana Staging Cloud environment
Host OS and Browser version:
Windows, All
Preconditions
Steps to reproduce:
Actual Result:
Agent logging level is not updated even on hard refreshing the browser.
Screenshots:
The text was updated successfully, but these errors were encountered: