Skip to content
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

Closed
blakerouse opened this issue Jun 12, 2020 · 6 comments
Assignees

Comments

@blakerouse
Copy link
Contributor

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.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Team:Ingest Management)

@michalpristas
Copy link
Contributor

we had a discussion with @ruflin and @ph somewhere on slack about this

i changed it to info
#18657

and reverted here
#18726

so we can get more information when raising issues until 8.0

@blakerouse
Copy link
Contributor Author

blakerouse commented Jun 13, 2020 via email

@ruflin
Copy link
Contributor

ruflin commented Jun 15, 2020

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.

@michalpristas
Copy link
Contributor

yes we can change event level on restart. this will change both agent and beats level.
we support trace, debug, info and error
we differentiate between trace and debug but beats does not have a notion of trace level so we use debug when trace is used

@michalpristas
Copy link
Contributor

closing as we moved to info log level recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants