Precedence and Specificity Rules

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. Severity
6. Product

Configuration Example

• 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').
• Custom Setting 5: Matches Category (“Network and Traffic”), Sub-Category (“Site/Tunnel”), Code ([“INC_RN_SITE_DOWN”]), and Severity ([Critical]).
• Custom Setting 6: Matches Category (“Network and Traffic”), Sub-Category (“Site/Tunnel”), Code ([“INC_RN_SITE_DOWN”]), and Severity ([High, Warning]).

• 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.

• 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.

• Incident: Code INC_RN_SITE_DOWN with severity Critical occurring on site REMOTE SITE A.
• Result: Strata Cloud Manager applies Custom Setting 5.
• Reasoning: Custom Setting 5 matches the incident severity (Critical) and provides a more specific match than Custom Setting 3 (which has no severity filter). A setting with an explicit severity filter takes priority over a setting that matches any severity when the incident severity matches the filter.
• Fallback: If you delete Custom Setting 5, Strata Cloud Manager applies Custom Setting 3, as it matches all severities (severity_filter = ANY).

• Incident: Code INC_RN_SITE_DOWN with severity High occurring on site REMOTE SITE A.
• Result: Strata Cloud Manager applies Custom Setting 6.
• Reasoning: The Custom Setting 6 severity filter ([High, Warning]) includes the incident severity (High). Strata Cloud Manager discards Custom Setting 5 because its severity filter ([Critical]) does not match the incident severity.
• Fallback: If you delete Custom Setting 6, Strata Cloud Manager applies Custom Setting 3 (severity_filter = ANY), which matches all severities.