hanahmily opened a new pull request, #1178:
URL: https://github.com/apache/skywalking-banyandb/pull/1178
## Summary
- **Root fix**: Lifecycle sidecar now resolves sender identity from
`POD_NAME` env var instead of gRPC address, so `pod_name` / `node_type` labels
on `banyandb_lifecycle_migration_*` and `banyandb_lifecycle_cycles_total`
metrics are correct on GKE (where the gRPC bind address is `0.0.0.0`, not a
resolvable hostname).
- **Metric refactor**: `cycles_total` and `last_run_*` metrics now carry
`remote_*` and `group` labels emitted correctly per-cycle; stale series from
previous cycles are deleted to avoid phantom time-series.
- **Grafana — new dashboard**
(`docs/operation/grafana-fodc-migration.json`): dedicated *BanyanDB — Lifecycle
Migration* dashboard covering health overview, cycle status, migration flows
(pub↔sub pairing), throughput, latency, and drift panels. Uses
`$job`/`$group`/`$operation` template vars — no `$role`/`$pod` coupling to the
data-container metrics.
- **Grafana — nodes dashboard** (`docs/operation/grafana-fodc-nodes.json`):
remove the Tier Migrations panel (moved to the new dashboard); keep Streaming
Flows panel; close the layout gap.
- **File-sync sub pairing fix**: refId B in the Migration Flows panel now
uses `total_finished{operation="file-sync"}` for the subscriber side, since the
chunked-sync receive path has no per-message counter (`total_message_started`
has no file-sync series).
## Test plan
- [ ] Verify `banyandb_lifecycle_migration_*` metrics on live cluster show
correct `pod_name` / `node_type` labels after the fix
- [ ] Confirm new Grafana dashboard loads from configmap and all panels
render without "No data"
- [ ] Confirm Tier Migrations panel is removed from Nodes dashboard and
layout has no gap
- [ ] Check pub↔sub drift panel shows ~0 for batch-write and file-sync
operations
- [ ] Run integration test: `test/cases/lifecycle_identity/` passes with
`POD_NAME=localhost`
--
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]
