-
Notifications
You must be signed in to change notification settings - Fork 2
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
NH-76996 - Disabled platform events log processing #25
Conversation
} else { | ||
r.logger.Error("error parsing time", zap.Error(err)) | ||
return plog.Logs{}, err | ||
} | ||
if el.Type == string(telemetryapi.Function) || el.Type == string(telemetryapi.Extension) { |
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.
I thought we agreed not to forward Extension events as logs?
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.
Yes, the logic is the same. The decision now is made from the subscription type.
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.
I see. Can we just not subscribe to anything other than Function events for this round to minimize overhead?
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.
Sure. Done
Disabled log forwarding by commenting out logs pipeline in config.yaml |
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.
Great, thanks!
* Disable platform events log stringify
Disabled platform events log processing
https://swicloud.atlassian.net/browse/NH-76996