[snmp] Re-categorize aruba-clearpass metric type fix as breaking change#23844
Merged
Conversation
Contributor
|
|
dkirov-dd
approved these changes
May 27, 2026
Contributor
Validation ReportAll 21 validations passed. Show details
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Renames the changelog entry for #23791 from
snmp/changelog.d/23791.fixedtosnmp/changelog.d/23791.changed. No code changes.Motivation
Follow-up to merged PR #23791, which corrected the metric type for four
cppmSystem*memory/disk metrics in the aruba-clearpass SNMP profile (rate → gauge). The change is functionally a fix, but the metric-type discontinuity is breaking for existing dashboards and monitors. Per review feedback from David, the entry should be categorized aschangedso the breaking nature is reflected in the next release's version bump rather than landing as a patch.Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged