-
Notifications
You must be signed in to change notification settings - Fork 77
feat: Update Apache receiver to use LoggingReceiverMacro
#1992
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
feat: Update Apache receiver to use LoggingReceiverMacro
#1992
Conversation
6904756 to
8c109d9
Compare
8c109d9 to
36df4e9
Compare
apps/common_logging_processors.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for implementing the idea of converting genericAccessLogParserAsInternalLoggingProcessor into an InternalLoggingProcessor!
Sorry, now i'm realizing that the idea of converting it to an InternalLoggingProcessor was faulty because :
- The resulting processor
GenericAccessLogParserdependent onfluentbit.Component, which makes it not agent agnostic (e.g this would require an otel implementation too). - It doesn't necessarily improve the readability.
My recommendation is to revert it back to only use genericAccessLogParserAsInternalLoggingProcessor during the migration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note : This changes are expected.
36df4e9 to
3e1580c
Compare
9e89e69 to
d3cf3ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
d3cf3ca to
1cbe87b
Compare
2294cf4 to
7fc19eb
Compare
5232108
into
GoogleCloudPlatform:master
Description
Refactor the apache receiver logging to be sub-agent agnostic.
Related issue
How has this been tested?
Updated
transformation_testandconfgenerator_test, confirmed the output ofoutput_fluentbit.yamlwas unchanged after refactoring the receiver.Checklist: