-
Notifications
You must be signed in to change notification settings - Fork 805
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
[Wf-Diagnostics] introduce emitter interface in w/f diagnostics #6309
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
... and 17 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
msg[DiagnosticsStartTime] = data.DiagnosticsStartTime | ||
msg[DiagnosticsEndTime] = data.DiagnosticsEndTime | ||
|
||
serializedMsg, err := json.Marshal(msg) |
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.
why not just serialize WfDiagnosticsUsageData
? It that to have some compatibility?
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.
am following whats done in visibility. will double check with Neil too
return err | ||
} | ||
|
||
pinotMsg := &indexer.PinotMessage{ |
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.
shouldn't this layer be visibility-store agnostic?
What changed?
Workflow Diagnostics has a emitter interface that produces messages to a kafka topic
Why?
this emitter will be used to emit usage logs from workflow diagnostics runs to a pinot table
How did you test it?
unit tests
Potential risks
Release notes
Documentation Changes