You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client takes labels or attributes fields that are defined by the developer while connecting to the nats-server
Nats-Server renders these properties in the monitor server endpoint "/connz"
Use case
Identify the client who takes differences in version or deploys environment, I cannot manage them since they are almost the same in the '/connz' endpoint. Of course, I can add metadata in the name, but it's not graceful and reliable.
By the way, I found 'tags' keyword in GenericFields it included by JWT Claims, I have no idea about the usage of this field.
Contribution
No response
The text was updated successfully, but these errors were encountered:
I know that, but it seems working with a latent rule in the case, and if I put too many external attributes in it, it looks so long that readability disappears.
Anyway, my purpose can be achieved by bypassing this feature, but I truly think, it's useful while developer want to manage their NATs connections.
Proposed change
Use case
Identify the client who takes differences in version or deploys environment, I cannot manage them since they are almost the same in the '/connz' endpoint. Of course, I can add metadata in the name, but it's not graceful and reliable.
By the way, I found 'tags' keyword in
GenericFields
it included by JWT Claims, I have no idea about the usage of this field.Contribution
No response
The text was updated successfully, but these errors were encountered: