You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ci] Sanitize transient metric labels before comparison (#7482)
## Which problem is this PR solving?
- Fixes#7475
## Description of the changes
- Implemented an extensible transient label suppression system that
normalizes known volatile labels before metric comparison:
Kafka topics: jaeger-spans-\d+ → jaeger-spans-
Configurable patterns: Easy to add new transient label types in the
future
```
TRANSIENT_LABEL_PATTERNS = {
# Main key: service/component identifier
'kafka': { # ← service (Level 1)
# Nested key: specific label name within that service
'topic': { # ← label (Level 2)
# Configuration values
'pattern': r'jaeger-spans-\d+', # ← Pattern to match
'replacement': 'jaeger-spans-' # ← Replacement value
}
}
}
```
## How was this change tested?
- Local scripts + test data
- CI did not generate metric change with this change.
## Checklist
- [ ] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [ ] I have signed all commits
- [ ] I have added unit tests for the new functionality
- [ ] I have run lint and test steps successfully
- for `jaeger`: `make lint test`
- for `jaeger-ui`: `npm run lint` and `npm run test`
---------
Signed-off-by: Harshil Gupta <[email protected]>
0 commit comments