mirror of
https://github.com/alibaba/canal.git
synced 2026-11-04 00:30:15 +08:00
Updated Canal prometheus (markdown)
@@ -4,7 +4,7 @@ Canal server 性能指标监控基于prometheus的实现。
|
||||
|
||||
关于prometheus,参见[官网](https://prometheus.io/)
|
||||
|
||||
## 当前监控的canal相关原始指标列表:
|
||||
## canal监控相关原始指标列表:
|
||||
|
||||
| 指标 | 说明 | 单位 | 精度 |
|
||||
| :---- | :---- | ----: |----: |
|
||||
@@ -29,6 +29,22 @@ Canal server 性能指标监控基于prometheus的实现。
|
||||
|canal_instance_store_produce_mem |instance store接收到的所有events占用内存总量|byte|-|
|
||||
|canal_instance_store_consume_mem |instance store成功消费的所有events占用内存总量|byte|-|
|
||||
|
||||
## 监控展示指标
|
||||
| 指标 | 简述 |多指标|
|
||||
| :---- | :---- | :----: |
|
||||
|Basic|Canal instance 基本信息。|是|
|
||||
|Network bandwith|网络带宽。包含inbound(binlog读取)和outbound(向client输出)|是|
|
||||
|Delay|Canal instance 相对于master的延时。|否|
|
||||
|Idle|sink线程idle占比;dump线程idle占比(仅parallel mode)。|是|
|
||||
|TPS|Canal client instance消费binlog的TPS, 以MySQL binlog events为单位计算。|否|
|
||||
|TPS(transaction)|Canal instance 处理binlog的TPS,以MySQL transaction为单位计算。|否|
|
||||
|TPS(rows VS rowData)|Canal instance处理binlog的TPS,table rows:以table变更行为单位。row data:rowData events为单位。|是|
|
||||
|Client requests|Canal instance接收到的请求统计,结果按packet type分类。|否|
|
||||
|Latency|Canal client 请求latency概况。|否|
|
||||
|Empty packets|server响应GET请求,但返回空包的占比。|是|
|
||||
|Store remain events|Canal instance ringbuffer内未释放的events数量。|否|
|
||||
|Store remain mem|Canal instance ringbuffer 内未释放events占用内存。|否|
|
||||
|
||||
## JVM 相关信息
|
||||
> The Java client includes collectors for garbage collection, memory pools, JMX, classloading, and thread counts. These can be added individually or just use the DefaultExports to conveniently register them.
|
||||
> >DefaultExports.initialize();
|
||||
|
||||
Reference in New Issue
Block a user