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
This is an experimental proposal. In addition to implementation feedback, we are looking for
feedback on whether the configuration schema presents tag-value aggregation coherently.
Add per-metric tag-value filtering to metric_tag_filterlist before aggregation.
Allow configured tag values and remove or replace mismatches with a sentinel.
Require complete tag values to match a regular expression and replace non-matches.
Reject invalid or conflicting rules at startup; retain the last valid rules after invalid runtime updates.
Document current behavior and configuration-schema trade-offs.
Change Type
Bug fix
New feature
Non-functional (chore, refactoring, docs)
Performance
How did you test this PR?
Ran all 51 tag-filterlist unit tests, including new coverage for allowlists, regular expressions, conflicts, origin tags, and dynamic updates.
Run ID:b6e98b35-906d-4cd0-956d-0e5b0cf3062c Baseline:5e5efc94 · Comparison:5ee7dad2 · diff
Optimization Goals: ✅ No significant changes detected
Fine details of change detection per experiment (5)
Experiments configured erratic: true are tagged (ignored) and skipped when determining which experiments regressed or improved. Experiments which are detected as erratic at runtime are tagged (erratic) to flag that the run's sample dispersion was high, but their regression / improvement signal still counts.
A change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression (is_regression: true). Improvements use the matching criteria for the improving direction. Experiments configured erratic: true (tagged (ignored)) are skipped outright; experiments detected as erratic at runtime (tagged (erratic)) still count, since that flag describes sample dispersion rather than directional certainty. The Δ mean % cell is colored accordingly: 🟢 = improvement, 🔴 = regression, ⚪ = neutral. Reduction in CPU or memory is an improvement; reduction in ingress throughput is a regression.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
area/docsReference documentation.type/experimentA change that is still currently being worked on or tested to prove viability.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Note
This is an experimental proposal. In addition to implementation feedback, we are looking for
feedback on whether the configuration schema presents tag-value aggregation coherently.
Add per-metric tag-value filtering to
metric_tag_filterlistbefore aggregation.Change Type
How did you test this PR?
cargo check --workspace.cargo check --workspace --tests.git diff --check.References
N/A