-
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
[Elastic Agent] Starting beats with log level of trace causes every event to be logged #19179
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
I agree that having more information is great, but having every event in
the log will fill up the local disk and make it harder to parse a log to
help with debugging.
We should see if we can keep it the way it is, but turn off just the
logging of each event.
…On Sat, Jun 13, 2020, 2:14 AM Michal Pristas ***@***.***> wrote:
we had a discussion with @ruflin <https://github.com/ruflin> and @ph
<https://github.com/ph> somewhere on slack about this
i changed it to info
#18657 <#18657>
and reverted here
#18726 <#18726>
so we can get more information when raising issues until 8.0
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19179 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5QXZ764FJHRZZPPSZ6RXTRWMKMBANCNFSM4N4VVOBQ>
.
|
My end goal is to have info by default but allow users to dynamically enable debug if needed. A first step should be to allow it at least on restart to change (@michalpristas do we already have this)? And +1 on the proposal from @blakerouse to be more specific on what trace means and remove some of the data if we can. |
yes we can change event level on restart. this will change both agent and beats level. |
closing as we moved to |
I noticed that running the Elastic Agent that all the started beats are started in trace mode. While this helps with debugging it also currently causes all events to be logged to the log for that running beat.
I think we should either lower the logging level to ensure that every event is not logged, or adjust the debug selector to ensure that events are not logged.
The text was updated successfully, but these errors were encountered: