Skip to content

bridge-monitor: fix execution metrics label cardinality #1141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flotapponnier merged 1 commit into from
Jul 13, 2026
Merged

bridge-monitor: fix execution metrics label cardinality #1141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions harnesses/bridge-monitor/cmd/monitor/executor.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -899,6 +899,12 @@ func (e *Executor) recordExecutionMetrics(result *ExecutionResult) {
result.Route.ToToken,
amountStr,
e.region,
// chain dimension label, same convention as every quote path
// (mobula_bridge.go etc). This 8th label was missed when the
// metrics gained the chain dimension, and because execution was
// paused in prod the mismatch only surfaced at the first real
// single-test (panic: inconsistent label cardinality).
result.Route.ToChain,
}

// Record latencies
Expand Down
Loading