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
Change the pulsar_client_sending_buffers_count metric to client level (#1408)
#1394 introduces the `pulsar_client_sending_buffers_count` metric to track how many buffers are allocated for send purpose and not put back to the pool. However, unlike other metrics, this metric is not client level, so it cannot be attached with `CustomMetricsLabels` in client options.
When a send buffer was not put back to the pool, it means the `Release` method is not called due to some reason. Changing this metric to client level could help locate which client has triggered this bug in an application that has many client instances from different businesses.
Here is an example metric when I configured `CustomMetricsLabels: map[string]string{"key": "value"}` after this change
```
pulsar_client_sending_buffers_count{client="go",key="value"} 1
```
0 commit comments