-
Notifications
You must be signed in to change notification settings - Fork 165
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
Capture kafka cluster.id #32
Comments
FYI @pyohannes |
We'll consider this in the messaging workgroup (once we discuss attributes). |
The cluster id can be used to uniquely identify a cluster, even if host names, IP addresses, or ports change (see here for more details). In my opinion it makes sense to include the attribute, I'll bring it up in the next workgroup meeting. |
There was a consensus in the messaging workgroup that adding the attribute for cluster id makes sense. @jack-berg would you be willing to open a PR adding the attribute? |
What are you trying to achieve?
Kafka clusters have an identifier called cluster_id that is useful in environments with multiple clusters. For example, you may have clusters for different domains, or you may have use something like MirrorMaker to copy data between two clusters.
In these situations, its useful for
cluster_id
to be included in telemetry data. I propose that we addcluster_id
as a kafka specific attribute in the messaging semantic conventions.Additional context.
Unclear if this has already been considered.
The text was updated successfully, but these errors were encountered: