>
    Strata Copilot
    inspect performance-policy lookup
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma SD-WAN
    3. Use CLI Commands
    4. Inspect Commands
    5. inspect performance-policy lookup
    Download PDF
    Prisma SD-WAN

    inspect performance-policy lookup

    Table of Contents

    inspect performance-policy lookup

    Use the inspect performance-policy lookup command to determine which performance policy rule applies to traffic based on the current site IP and destination IP address or IP prefix.
    Use the inspect performance-policy lookup command to confirm which performance policy rules apply to a given path, application, or system health metric. The output shows the matched rule and policy set, the configured thresholds, the app and path filters in effect, and the configured action when a monitored metric crosses a threshold. Use this command to verify that the correct policy applies before a threshold event occurs, or to understand why a specific rule did or did not trigger an action on live traffic.

    Command

    inspect performance-policy lookup ( application= appID_or_appName | path-id= pathID |
    threshold-type= <app-perf | lqm-perf> | health-type= <cpu | memory | disk | circuit | flow-util> )

    Options

    applicationEnter an application ID or name to display performance policy rules that apply to that application.
    health-typeEnter the health type to display performance policy thresholds for system health, metrics health, system performance, or circuit utilization. Accepted values are cpu, memory, disk, circuit, and flow-util.
    path-idEnter a path ID to display performance policy rules that apply to that path.
    threshold-typeEnter the threshold type to filter results. Use lqm-perf for Link Quality Metrics thresholds or app-perf for application performance thresholds.

    When to Use

    • Before a threshold event occurs, to confirm the threshold values and scope of the rule that applies to a specific path or application.
    • When a performance policy action did not trigger during a known degradation event, to confirm whether the path or application falls within the rule's scope.
    • When multiple performance policy rules exist, to determine which one takes precedence for a specific path-application combination.

    Command Notes

    RoleSuper, Read Only, Monitor
    Related CommandsNone
    Introduced inRelease 6.3.1

    Example

    The following example displays performance policy rules that apply to a specific path:
    inspect performance-policy lookup path-id=1699889670704015737
Requested PathID: 1699889670704015737

Performance Policy Rule         : Default-PerfMgmtRule-Visibility (1690882969061024037)
Performance Policy Rule Num     : 1
Performance Policy Set          : Default-PerfMgmtPolicySet (1690882969054023637)
Performance Policy Stack        : Default-PerfMgmtPolicySetStack (1690882969064024237)
App Filters                     :
    App Transfer Types          :
    Applications                :
Path Filters                    :
Service Labels                  :
Lqm Thresholds                  :
    MaxJitter                   : 40
    MaxLatency                  : 150
    MaxPacketLoss               : 2
Actions                         :
    Action Type                 : visibility

    Output Fields

    • Performance Policy Rule: The name and ID of the matched rule.
    • Performance Policy Rule Num: The evaluation order of the rule within the policy set.
    • Performance Policy Set: The policy set the rule belongs to.
    • Performance Policy Stack: The policy set stack that contains the rule.
    • App Filters: The application transfer types and specific applications in the rule's scope. Empty means the rule applies to all applications.
    • Path Filters: The paths in the rule's scope. Empty means the rule applies to all paths.
    • Service Labels: Any service labels that narrow the rule's scope.
    • Lqm Thresholds: The Link Quality Metrics threshold values configured in the rule, including maximum jitter (ms), latency (ms), and packet loss (%).
    • Actions: The configured action when a monitored metric crosses a threshold, such as visibility or path steering.

    Troubleshooting

    ConditionPossible CauseAction
    No rule is returned for a known path IDThe path is not within the scope of any performance policy rule's path filterReview path filters in the controller; verify the path's service label or type matches the rule scope
    A rule is returned but the expected action is not triggeringThe Lqm Thresholds in the matched rule are set more conservatively than the observed degradation level, or the monitoring approach requires more samples before triggeringCompare the displayed threshold values against actual observed metrics on the path; consider lowering thresholds or switching to a more aggressive monitoring approach
    The wrong rule is returned for an applicationMultiple rules match the application, and a higher-priority rule is taking precedenceReview rule ordering within the policy set stack in the controller and adjust priority as needed

    © 2026 Palo Alto Networks, Inc. All rights reserved.