momo-jun commented on code in PR #15447:
URL: https://github.com/apache/pulsar/pull/15447#discussion_r866466326
##########
site2/docs/reference-metrics.md:
##########
@@ -117,6 +117,34 @@ The following metrics are available for broker:
- [Pulsar SQL Worker](#pulsar-sql-worker)
- [Pulsar transaction](#pulsar-transaction)
+### Broker metrics
+All the broker metrics are labelled with the following labels:
+- cluster: cluster=${pulsar_cluster}. ${pulsar_cluster} is the cluster name
that you have configured in the `broker.conf` file.
+
+| Name | Type | Description |
+|---|---|---|
+| pulsar_ml_cache_evictions | Gauge | The number of cache evictions during
the last minute. |
+| pulsar_ml_cache_hits_rate | Gauge | The number of cache hits per second on
the broker side. |
+| pulsar_ml_cache_hits_throughput | Gauge | The amount of data is retrieved
from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_misses_rate | Gauge | The number of cache misses per second
on the broker side. |
+| pulsar_ml_cache_misses_throughput | Gauge | The amount of data is not
retrieved from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_pool_active_allocations | Gauge | The number of currently
active allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_huge | Gauge | The number of
currently active huge allocation in direct arena |
+| pulsar_ml_cache_pool_active_allocations_normal | Gauge | The number of
currently active normal allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_small | Gauge | The number of
currently active small allocations in direct arena |
+| pulsar_ml_cache_pool_allocated | Gauge | The total allocated memory of
chunk lists in direct arena |
+| pulsar_ml_cache_pool_used | Gauge | The total used memory of chunk lists in
direct arena |
+| pulsar_ml_cache_used_size | Gauge | The size in byte used to store the
entries payloads |
+| pulsar_ml_count | Gauge | The number of currently opened managed ledgers |
+| topic_load_times | Summary | The topic load latency calculated in
milliseconds |
+| pulsar_active_connections| Gauge | The number of active connections |
+| pulsar_connection_created_total_count | Gauge | The total number of
connections |
+| pulsar_connection_create_success_count | Gauge | The number of successfully
created connections |
+| pulsar_connection_create_fail_count | Gauge | The number of failed
connections |
+| pulsar_connection_closed_total_count | Gauge | The total number of closed
connections |
+| pulsar_broker_throttled_connections | Gauge | The number of throttled
connections |
+| pulsar_broker_throttled_connections_global_limit | Gauge | The number of
throttled connections because of per-connection limit |
Review Comment:
```suggestion
| pulsar_broker_throttled_connections_global_limit | Gauge | The number of
throttled connections due to per-connection limit. |
```
##########
site2/docs/reference-metrics.md:
##########
@@ -117,6 +117,34 @@ The following metrics are available for broker:
- [Pulsar SQL Worker](#pulsar-sql-worker)
- [Pulsar transaction](#pulsar-transaction)
+### Broker metrics
+All the broker metrics are labelled with the following labels:
+- cluster: cluster=${pulsar_cluster}. ${pulsar_cluster} is the cluster name
that you have configured in the `broker.conf` file.
+
+| Name | Type | Description |
+|---|---|---|
+| pulsar_ml_cache_evictions | Gauge | The number of cache evictions during
the last minute. |
+| pulsar_ml_cache_hits_rate | Gauge | The number of cache hits per second on
the broker side. |
+| pulsar_ml_cache_hits_throughput | Gauge | The amount of data is retrieved
from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_misses_rate | Gauge | The number of cache misses per second
on the broker side. |
+| pulsar_ml_cache_misses_throughput | Gauge | The amount of data is not
retrieved from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_pool_active_allocations | Gauge | The number of currently
active allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_huge | Gauge | The number of
currently active huge allocation in direct arena |
+| pulsar_ml_cache_pool_active_allocations_normal | Gauge | The number of
currently active normal allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_small | Gauge | The number of
currently active small allocations in direct arena |
+| pulsar_ml_cache_pool_allocated | Gauge | The total allocated memory of
chunk lists in direct arena |
+| pulsar_ml_cache_pool_used | Gauge | The total used memory of chunk lists in
direct arena |
+| pulsar_ml_cache_used_size | Gauge | The size in byte used to store the
entries payloads |
+| pulsar_ml_count | Gauge | The number of currently opened managed ledgers |
+| topic_load_times | Summary | The topic load latency calculated in
milliseconds |
+| pulsar_active_connections| Gauge | The number of active connections |
+| pulsar_connection_created_total_count | Gauge | The total number of
connections |
+| pulsar_connection_create_success_count | Gauge | The number of successfully
created connections |
+| pulsar_connection_create_fail_count | Gauge | The number of failed
connections |
+| pulsar_connection_closed_total_count | Gauge | The total number of closed
connections |
+| pulsar_broker_throttled_connections | Gauge | The number of throttled
connections |
Review Comment:
```suggestion
| pulsar_broker_throttled_connections | Gauge | The number of throttled
connections. |
```
##########
site2/docs/reference-metrics.md:
##########
@@ -117,6 +117,34 @@ The following metrics are available for broker:
- [Pulsar SQL Worker](#pulsar-sql-worker)
- [Pulsar transaction](#pulsar-transaction)
+### Broker metrics
+All the broker metrics are labelled with the following labels:
+- cluster: cluster=${pulsar_cluster}. ${pulsar_cluster} is the cluster name
that you have configured in the `broker.conf` file.
+
+| Name | Type | Description |
+|---|---|---|
+| pulsar_ml_cache_evictions | Gauge | The number of cache evictions during
the last minute. |
+| pulsar_ml_cache_hits_rate | Gauge | The number of cache hits per second on
the broker side. |
+| pulsar_ml_cache_hits_throughput | Gauge | The amount of data is retrieved
from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_misses_rate | Gauge | The number of cache misses per second
on the broker side. |
+| pulsar_ml_cache_misses_throughput | Gauge | The amount of data is not
retrieved from the cache on the broker side (in byte/s). |
+| pulsar_ml_cache_pool_active_allocations | Gauge | The number of currently
active allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_huge | Gauge | The number of
currently active huge allocation in direct arena |
+| pulsar_ml_cache_pool_active_allocations_normal | Gauge | The number of
currently active normal allocations in direct arena |
+| pulsar_ml_cache_pool_active_allocations_small | Gauge | The number of
currently active small allocations in direct arena |
+| pulsar_ml_cache_pool_allocated | Gauge | The total allocated memory of
chunk lists in direct arena |
+| pulsar_ml_cache_pool_used | Gauge | The total used memory of chunk lists in
direct arena |
+| pulsar_ml_cache_used_size | Gauge | The size in byte used to store the
entries payloads |
+| pulsar_ml_count | Gauge | The number of currently opened managed ledgers |
+| topic_load_times | Summary | The topic load latency calculated in
milliseconds |
+| pulsar_active_connections| Gauge | The number of active connections |
+| pulsar_connection_created_total_count | Gauge | The total number of
connections |
+| pulsar_connection_create_success_count | Gauge | The number of successfully
created connections |
+| pulsar_connection_create_fail_count | Gauge | The number of failed
connections |
+| pulsar_connection_closed_total_count | Gauge | The total number of closed
connections |
Review Comment:
```suggestion
| pulsar_connection_closed_total_count | Gauge | The total number of closed
connections. |
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
