feat(go): expose async sink publish latency histogram
This commit is contained in:
@@ -393,6 +393,9 @@ net.ipv4.tcp_tw_reuse = 1
|
||||
vehicle_async_sink_enqueue_total{sink,kind,status}
|
||||
vehicle_async_sink_publish_total{sink,kind,status}
|
||||
vehicle_async_sink_publish_duration_ms{sink,kind,status}
|
||||
vehicle_async_sink_publish_duration_ms_histogram_bucket{sink,kind,status,le}
|
||||
vehicle_async_sink_publish_duration_ms_histogram_count{sink,kind,status}
|
||||
vehicle_async_sink_publish_duration_ms_histogram_sum{sink,kind,status}
|
||||
vehicle_async_sink_queue_depth{sink}
|
||||
```
|
||||
|
||||
@@ -404,7 +407,7 @@ vehicle_async_sink_queue_depth{sink}
|
||||
- NATS bridge ack pending 为 `0`
|
||||
- Gateway 启动后窗口无 `error|failed|panic|fatal` 日志
|
||||
|
||||
这些指标是进入带帧率压测前的关键保护栏:如果 `queue_depth` 持续增长或 `enqueue_total{status="timeout"}` 增长,说明入口 publish 队列已成为瓶颈。
|
||||
这些指标是进入带帧率压测前的关键保护栏:如果 `queue_depth` 持续增长、`enqueue_total{status="timeout"}` 增长,或 `vehicle_async_sink_publish_duration_ms_histogram_bucket` 的 p99 持续上升,说明入口 publish 队列或下游 NATS/Kafka 写入已成为瓶颈。
|
||||
|
||||
### NATS Kafka bridge batch 指标
|
||||
|
||||
|
||||
Reference in New Issue
Block a user