-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Metrics] Add the broker connection metrics. #9876
[Metrics] Add the broker connection metrics. #9876
Conversation
@congbobo184 thanks for your work. Would you like to add docs accordingly? Then we can help review, thanks |
@Anonymitaet Ok I will add the doc. |
@@ -34,6 +35,11 @@ | |||
private final DimensionStats zkWriteLatencyStats; | |||
private final DimensionStats zkReadLatencyStats; | |||
private final String brokerName; | |||
private final AtomicLong connectionTotalCreatedCount; |
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.
Prefer LongAdder
instead of AtomicLong
since it will have less contention issues.
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.
OK i will change the atomicLong to LongAdder.
/pulsarbot run-failure-checks |
Co-authored-by: Yu Liu <50226895+Anonymitaet@users.noreply.github.com>
Co-authored-by: Yu Liu <50226895+Anonymitaet@users.noreply.github.com>
## Motivation Add the broker connection metrics. ## implement add metrics ``` brk_connection_created_total_count brk_connection_create_success_count brk_connection_create_fail_count brk_connection_closed_total_count brk_active_connections ```
Motivation
Add the broker connection metrics.
implement
add metrics
Verifying this change
Add the tests for it
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)