Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for this project! ❤️
I've noticed an opportunity to enhance observability from the broker's perspective.
Firstly, introducing a feature to set a human-friendly connection name would greatly improve the ability to distinguish connections easily.
Secondly, providing additional information in client properties could be useful in identifying issues with applications, such as the application version.
With this pull request, I propose adding two additional configuration options:
connection_name
- to set the connection name conveniently. It can be easily controlled with theHUTCH_CONNECTION_NAME
environment variable, requiring no explicit configuration.mq_client_properties
- to manage all client properties, including theconnection_name
.Before
After