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
Zap Field Attributes Reporting #902
Conversation
@@ -582,6 +582,10 @@ type ApplicationLogging struct { | |||
// Toggles whether the agent enriches local logs printed to console so they can be sent to new relic for ingestion | |||
Enabled bool | |||
} | |||
ZapLogger struct { |
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.
Could we add more info here about when it makes sense to do this: We want to enable this when your app collects fewer logs, or if your app can afford to compile the json during log collection, slowing down the execution of the line of code that will write the log. Otherwise, if your application collects logs at a high frequency or volume, or it can not afford the slowdown of marshaling objects before sending them to newrelic, we can marahal them asynchronously in the backend during harvests
one nit pick, otherwise lgtm |
Adds support for Zap field attributes properly showing up on the New Relic Platform.