docs: record go topic configuration baseline

This commit is contained in:
lingniu
2026-07-02 21:05:46 +08:00
parent bec6326103
commit da78a989b5

View File

@@ -25,6 +25,19 @@
| 统计 | MySQL stat writer | `lingniu-go-stat-writer.service` | `127.0.0.1:20213` |
| 实时 | Realtime API/projector | `lingniu-go-realtime-api.service` | `127.0.0.1:20200` |
## Topic 配置基线
生产环境的 env 文件必须和 Go topic 命名空间保持一致:
| 服务 | 必要 topic |
| --- | --- |
| `lingniu-go-history-writer.service` | `vehicle.raw.go.gb32960.v1``vehicle.raw.go.jt808.v1``vehicle.raw.go.yutong-mqtt.v1` |
| `lingniu-go-stat-writer.service` | `vehicle.raw.go.gb32960.v1``vehicle.raw.go.jt808.v1``vehicle.raw.go.yutong-mqtt.v1` |
| `lingniu-go-realtime-api.service` | `vehicle.event.go.unified.v1` |
| `lingniu-go-nats-kafka-bridge.service` | NATS subjects 到同名 Kafka topic包含三条 raw.go topic 和一条 unified topic |
如果 stat-writer 少消费某个 raw topic对应协议的每日里程不会进入 `vehicle_daily_mileage`。修正后可能出现短时间 Kafka lag这是在追补历史 backlog只要 `vehicle_stat_writes_total` 持续增长且 lag 下降,就是健康状态。
业务端口:
- GB32960 TCP`0.0.0.0:32960`