feat(go): expose fast writer stage latency histogram
This commit is contained in:
@@ -409,6 +409,18 @@ vehicle_async_sink_queue_depth{sink}
|
||||
|
||||
这些指标是进入带帧率压测前的关键保护栏:如果 `queue_depth` 持续增长、`enqueue_total{status="timeout"}` 增长,或 `vehicle_async_sink_publish_duration_ms_histogram_bucket` 的 p99 持续上升,说明入口 publish 队列或下游 NATS/Kafka 写入已成为瓶颈。
|
||||
|
||||
### NATS fast writer stage histogram
|
||||
|
||||
2026-07-03 已为 NATS fast writer 增加阶段耗时 histogram:
|
||||
|
||||
```text
|
||||
vehicle_fast_writer_stage_duration_ms_histogram_bucket{subject,stage,status,le}
|
||||
vehicle_fast_writer_stage_duration_ms_histogram_count{subject,stage,status}
|
||||
vehicle_fast_writer_stage_duration_ms_histogram_sum{subject,stage,status}
|
||||
```
|
||||
|
||||
`stage` 取值包括 `tdengine`、`redis`、`ack`,分别对应快速写 TDengine raw/location、Redis realtime 投影、NATS ack。带帧率压测时如果某个 stage 的 p99 持续上升,可以直接定位 fast path 是存储瓶颈还是 ack/网络瓶颈。
|
||||
|
||||
### NATS Kafka bridge batch 指标
|
||||
|
||||
2026-07-03 已为 NATS -> Kafka bridge 增加 batch pending 和 duration histogram:
|
||||
|
||||
Reference in New Issue
Block a user