An event in Dynatrace has a type and severity (significance) level.
- Resulting problems aggregate all included event severities and are evaluated with the highest severity level of the constituent events.
- During its lifespan, a problem might raise its severity level. For example, a problem might begin in slowdown level (3) and then be raised automatically to availability level (1) when an outage is detected.
In order from most to least severe, the event types supported in Dynatrace are as follows:
Severity 1: Availability
Availability events indicate high-severity incidents within your environment, such as a complete outage or unavailability of servers or processes.
Severity 2: Error
Error events inform you of increased error rates or other error-related incidents that interfere with the regular operation of your environment.
Severity 3: Slowdown
Slowdown events indicate a decrease of performance in one of your operational services or applications.
- While slowdown events are less severe than error or availability events, they inform you of potential issues with the performance of your services.
Severity 4: Resource
Resource events indicate resource contention. Typical examples:
- CPU saturation
- Memory saturation
Severity 5: Custom
Custom alerts are used to enable alerting on any user-defined thresholds.
- Custom alerts for user-defined thresholds can be set for any Dynatrace metric.
- Custom alerts aren't correlated or modified by Davis, although they are automatically alerted on.
Severity 6: Info
Info events indicate manually triggered events that don't result in the creation of a new problem, such as:
- Important deployments or configuration changes
- Administrative events (for example, automatic migration of a virtual machine)
Informational events aren't sent out as alerts and no problems are opened, as this type of event doesn't indicate an abnormal situation.