Review known issues regarding incidents and alerts.
Review the issues in Incidents and Alerts that we're working to fix.
ID
Description
AIOPS-8242
Notification Profile creation and updates could not occur due to an
improper configuration sent in the API. Notification profile
creation, update, and deletion with email, webhook, and ServiceNow
integration work as expected.
AIOPS-6019
When an incident is disabled in Incident Settings, future incidents
are suppressed. Incidents that are already raised incidents will
stay in raised state. When the raised incident is cleared, the
default notification profile is used to notify the customer, and the
notification profiles from the incident settings are not used.
AIOPS-5991
If the incident policies (with different notification profiles) that
match Raised Incidents are removed, the Clear Incident event is
published using default notification profile.
AIOPS-4445
When two people are configuring or modifying the same notification
profile, only the final changes are reflected.
AIOPS-4401
SPN Capacity incidents
INC_RN_SPN_LONG_DURATION_CAPACITY_EXCEEDED_THRESHOLD and
INC_RN_SPN_LONG_DURATION_EXCEEDED_CAPACITY will not be blocked at
the RN site classification level, because there is no resource_key
or resource_context of site_name used. Customers may be confused by
being able to create Incident Settings rules for this code, as the
site classification doesn't work.
AIOPS-3540
On the
Incidents and Alerts: Prisma Access
Incident Settings
page, if you create custom CODE rules, CATEGORY rules
may never get triggered.