Incident Setting Resolution
Focus
Focus
Strata Cloud Manager

Incident Setting Resolution

Table of Contents

Incident Setting Resolution

Learn about the incident settings resolution.
Where Can I Use This?What Do I Need?
  • One of the following licenses:
This topic outlines the logic used to determine which setting applies to a specific incident when multiple settings match. Strata Cloud Manager resolves conflicts using precedence and longest match criteria.

Precedence and Specificity Rules

To select the definitive setting, the Strata Cloud Manager evaluates all applicable settings based on the following hierarchy:
  1. Custom vs. Default Precedence:
    Custom Settings take precedence over Default Settings. If an incident matches the criteria of any Custom Setting, the Default Settings are overridden.
  2. Longest Match Logic:
    Among the applicable Custom Settings, Strata Cloud Manager prioritizes Custom Settings based on specificity. The configuration with the highest degree of specificity, determined by the maximum number of matching fields, takes precedence. Settings that match more specific fields override settings that match only general fields.
    The fields are evaluated in the following order of specificity (from most specific to least specific):
  1. Objects (e.g., specific site_name or entity ID)
  2. Code
  3. Sub-Category
  4. Category
  5. Product

Configuration Example

Consider a scenario where the following settings exist for a specific Tenant Service Group:
  • Default Setting 0: Matches Category ('Network and Traffic'), Sub-Category ('Site/Tunnel'), and Code (['INC_RN_SITE_DOWN']).
  • Custom Setting 1: Matches Category ('Network and Traffic').
  • Custom Setting 2: Matches Category ('Network and Traffic') and Sub-Category ('Site/Tunnel').
  • Custom Setting 3: Matches Category ('Network and Traffic'), Sub-Category ('Site/Tunnel'), and Code (['INC_RN_SITE_DOWN']).
  • Custom Setting 4: Matches Category ('Network and Traffic'), Sub-Category ('Site/Tunnel'), Code (['INC_RN_SITE_DOWN']), and Objects (site_name = 'SDWAN LAB C8500').
Here are the resolution scenarios:
Scenario A: Exact Object Match
  • Incident: Code INC_RN_SITE_DOWN occurring on site SDWAN LAB C8500.
  • Result: Custom Setting 4 is applied.
  • Reasoning: While Custom Settings 1, 2, 3, and 4 are all technically valid, Custom Setting 4 provides the longest match by including the specific Objects field.
  • Fallback: If Custom Setting 4 were deleted, the Strata Cloud Manager would apply Custom Setting 3, as it becomes the next most specific match.
Scenario B: General Match (Different Site)
  • Incident: Code INC_RN_SITE_DOWN occurring on site REMOTE SITE A.
  • Result: Custom Setting 3 is applied.
  • Reasoning: Custom Setting 4 is discarded because the Objects criteria ('SDWAN LAB C8500') does not match 'REMOTE SITE A'. Among the remaining applicable settings (1, 2, and 3), Custom Setting 3 is the most specific.