-
Notifications
You must be signed in to change notification settings - Fork 24.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
Logging: Clean up logger building #32174
Comments
Pinging @elastic/es-core-infra |
Hey @nik9000, what do you mean by:
|
We have this This is one of those "lets not have 12 ways of doing things just because we accumulated them over the years" initiatives. For the most part the change it super easy and mechanical, it is just that someone has to do them. I've been doing a bunch of them over the past few months but some helpful folks told me last week that I should document my plan for the end state. This is that. |
Got it! Thanks! So basically step 3. is to finally remove |
Right!
Awesome! |
Replace deprecated Loggers calls with LogManager. Relates to #32174
Replace deprecated Loggers calls with LogManager. Relates to #32174
Drop the last function from `Loggers` that just wraps Log4j2. Relates to elastic#32174
Thanks @pratiksanglikar and @lipsill for doing the heavy lifting here! |
Replace deprecated Loggers calls with LogManager. Relates to #32174
Drop the last function from `Loggers` that just wraps Log4j2. Relates to #32174
`ESLoggerFactory` is now not particularly interesting and simple enought to fold entirely into `Loggers. So let's do that. Closes elastic#32174
Drop the last function from `Loggers` that just wraps Log4j2. Relates to #32174
`ESLoggerFactory` is now not particularly interesting and simple enought to fold entirely into `Loggers. So let's do that. Closes #32174
`ESLoggerFactory` is now not particularly interesting and simple enought to fold entirely into `Loggers. So let's do that. Closes #32174
We build loggers in about 15 different ways right now. After #31588 we'll only really need about 3 different ways. We should remove all of the confusing "variety".
The text was updated successfully, but these errors were encountered: