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

Req: support for in-place log4j i.e. no code change #834

Open
yan-hic opened this issue Aug 31, 2022 · 0 comments
Open

Req: support for in-place log4j i.e. no code change #834

yan-hic opened this issue Aug 31, 2022 · 0 comments
Labels
api: logging Issues related to the googleapis/java-logging-logback API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@yan-hic
Copy link

yan-hic commented Aug 31, 2022

We use legacy 3rd party software that uses deep log4j (2.x) and wish to send the logs async to GCP (logging but gcs in chunks is good too).
Unfortunately log4j-over-slf4j module does not work for us as the app imports classes which are not supported in the bridge.

Is there any plan to expand to other logging mechanisms ?

@product-auto-label product-auto-label bot added the api: logging Issues related to the googleapis/java-logging-logback API. label Aug 31, 2022
@losalex losalex self-assigned this Sep 7, 2022
@losalex losalex added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p3 Desirable enhancement or fix. May not be included in next release. labels Sep 7, 2022
@losalex losalex removed their assignment Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: logging Issues related to the googleapis/java-logging-logback API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants