inspect performance-policy hits analytics
Focus
Focus
Prisma SD-WAN

inspect performance-policy hits analytics

Table of Contents

inspect performance-policy hits analytics

Use the inspect performance-policy hits analytics command to display hit counts for performance policy analytics rules, showing how much traffic each rule has matched.
Use the inspect performance-policy hits analytics command to verify that performance policy rules trigger as expected when link quality crosses a configured threshold. The output shows cumulative hit counts alongside a New Hits counter that tracks activations since the last reset. Use the reset-diff option to zero the New Hits counter, then run diff-only after a period of time to see only the rules that triggered in that window. This workflow identifies rules that fire unexpectedly, confirms that policy changes take effect, and detects rules that have never matched a threshold breach.

Command

inspect performance-policy hits analytics threshold-type=lqm-perf ( all | diff-only | reset-diff )

Options

allDisplay hit count information for all performance policy rules.
diff-onlyDisplay only performance policy rules where the New Hits value is non-zero. Use after reset-diff to see rules triggered since the last reset.
reset-diffReset the New Hits counter to zero for all performance policy rules.

When to Use

  • When a performance policy action such as path steering or FEC is not occurring during a known degradation event, to confirm whether the threshold breach itself was detected.
  • Periodically, to identify rules that have accumulated zero hits, which may indicate a scope mismatch between the rule and the monitored paths or a threshold that is set too conservatively.

Command Notes

RoleSuper, Read Only, Monitor
Related Commands
inspect performance-policy lookup
Introduced inRelease 6.3.1

Example

The following example displays hit counts for all performance policy rules:
inspect performance-policy hits analytics threshold-type=lqm-perf Policy ID Performance Policy Name Total Hits New Hits 1690882969061024037 Default-PerfMgmtRule-Visibility 5 5 1701923892838000737 Filters 2 2
The following example uses diff-only to list only the rules that have recorded new hits since the last reset:
inspect performance-policy hits analytics threshold-type=lqm-perf diff-only Policy ID Performance Policy Name Total Hits New Hits 1690882969061024037 Default-PerfMgmtRule-Visibility 10 10 1701923892838000737 Filters 4 4

Output Fields

  • Policy ID: The numeric identifier of the performance policy rule.
  • Performance Policy Name: The name of the performance policy rule.
  • Total Hits: The cumulative number of times a threshold breach triggered this rule since the last system restart.
  • New Hits: The number of hits since the last reset-diff. Resets to zero when reset-diff runs.

Troubleshooting

ConditionPossible CauseAction
Total Hits is zero for a rule even though link quality is degradedThe rule's application or path filters exclude the degraded paths or applicationsUse inspect performance-policy lookup to confirm the rule scope includes the degraded path
A rule is triggering hits much more frequently than expectedThe raise threshold is set too low relative to normal traffic variation on the monitored pathsReview and raise the threshold value in the performance policy configuration in the controller
New Hits remain zero after reset-diff during a known degradation eventThe degradation may be on a path outside the rule's scope, or the monitoring approach requires more samples than the event durationCheck the monitoring approach (Conservative, Moderate, or Aggressive) and verify path scope with inspect performance-policy lookup