Right now problem notification filtering is on impact level (Application, Service, Infrastructure). This will be replaced with severity level filtering within the next 4 weeks. The new severity levels will be AVAILABILITY, ERROR, SLOWDOWN, RESSOURCE_CONTENTION and CUSTOM. See a screenshot of the new powerful notification filtering feature that is upcoming:
How we are going to decide which problem is more severe AVAILABILITY, ERROR, SLOWDOWN, RESOURCE_CONTENTION and CUSTOM.
The severity elevation logic is that AVAILABILITY comes first, followed by ERROR, SLOWDOWN and RESOURCE_CONTENTION. So a problem that starts as a SLOWDOWN will immediately raised to highest AVAILABILITY level once the Dynatrace AI detects any hint for an outage or host or process unavailability.
For availability, where can we find where the definition and do we have any control on what to alert on based on availability? (In DC RUM we have TCP Availability, Application availability, etc)
How we can map the priorities in Dynatrace (AVAILABILITY, ERROR, SLOWDOWN, RESOURCE_CONTENTION and CUSTOM) to the priorities in Jira (Blocker, Critical, Major, Minor and Trivial) ??