-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
(2.12) Server Metadata #6935
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
base: main
Are you sure you want to change the base?
(2.12) Server Metadata #6935
Conversation
6b50ef0
to
c749513
Compare
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.
some minor comments, but I didnt look at the details just behaviour
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.
What is the use case we are trying to solve here?
Sam as metadata on streams, consumers, buckets, k8s resources, etc - its let you put a bit of metadata in that other tools can read and catagorise or act on. For example monitoring data so those thresholds and such can be managed as configuration, or opt into monitoring (typical in k8s) lots of similar cases. |
c749513
to
330a005
Compare
Signed-off-by: Maurice van Veen <[email protected]>
Signed-off-by: Maurice van Veen <[email protected]>
Signed-off-by: Maurice van Veen <[email protected]>
Signed-off-by: Maurice van Veen <[email protected]>
330a005
to
26ca12c
Compare
Add
server_metadata
block to config, containing key-value pairs for server metadata. It can be config reloaded, and it's exposed in all Z endpoints (except for raftz).Resolves #6544
Signed-off-by: Maurice van Veen [email protected]