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

Improve Logging in Libbeat #5000

Closed
4 of 6 tasks
ruflin opened this issue Aug 24, 2017 · 5 comments
Closed
4 of 6 tasks

Improve Logging in Libbeat #5000

ruflin opened this issue Aug 24, 2017 · 5 comments
Assignees
Labels

Comments

@ruflin
Copy link
Contributor

ruflin commented Aug 24, 2017

Libbeat uses its own logging implementation. But the library has its limitation. This issue should be used as a meta issue to discuss potential issues with the library and also if moving forward the internal library should be improved or potentially replaced by either just and interface or a specific logging library as a dependency.

There are a few related Github issues which should be tracked with this Github issue:

This issue will be updated with new information.

@ruflin
Copy link
Contributor Author

ruflin commented Feb 26, 2018

@andrewkroh Could you have a look at the above ot check how many boxes we can check with your new implementation?

@andrewkroh
Copy link
Member

I ticked two more checkboxes.

@urso urso added the Team:Beats label Jan 3, 2020
@urso urso self-assigned this Jan 20, 2020
@andresrc andresrc added Team:Integrations Label for the Integrations team and removed Team:Beats labels Mar 6, 2020
@jlind23
Copy link
Collaborator

jlind23 commented Apr 1, 2022

Backlog grooming: Closing it for now until further activity, can still be reopened if needed.

@jlind23 jlind23 closed this as completed Apr 1, 2022
@acbox
Copy link

acbox commented Oct 20, 2022

This issue was closed with these two outstanding:

I'm here specifically because I would also like log level to be changed dynamically via HTTP. Any plans for this on the horizon? Thanks.

@andrewkroh
Copy link
Member

@acbox I saw a recent change at elastic/elastic-agent-libs#82 that makes the level changeable. I don't know if there are plans to expose this via an API.

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

No branches or pull requests

6 participants