-
Notifications
You must be signed in to change notification settings - Fork 27
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
Enhancement: custom header/metadata #30
Comments
Sounds reasonable, but keep in mind that the information we have available is typically just the record - if we wanted more info available to the exporter, then we should open an issue on the Zeebe repo to extend the exporter API. But I think your proposal is a good first step, if I understand correctly - we add a new config property where users can add static attributes (e.g. |
Yes, we were discussing this use case internally again yesterday. A new config property that holds a sub-map of static key-value pairs would be ideal for now. We would use this to include a cluster name/address as a header with messages, and perhaps an indicator if the cluster is currently is the primary one where we are starting new workflow instances. |
Hello everyone! |
@npepinpe |
Hello! It would be useful to be able to include additional, custom information with the messages that are published to Kafka.
The use case that I'm thinking of is running multiple Zeebe clusters (e.g. during a migration since horizontal scaling is not supported). Assuming, the same Kafka topics are reused, it would be useful to know which Zeebe cluster produced each event.
I was originally thinking that this could be supported by providing static attributes that would be merged into the JSON payload for each message.
But with Kafka support for headers, maybe this is better supported by specifying attributes to be included as headers in the exporter configuration.
What do you think?
The text was updated successfully, but these errors were encountered: