An event in Dynatrace can be of a specific type. Each event type has a defined severity level that indicates the significance of the incident. Resulting problems aggregate all included event severities and are evaluated with the highest severity level of the constituent events. During a problem's lifespan, a problem might raise its severity level (for example, a problem might begin in
slowdown level and then be automatically raised to the
availability level when an outage is detected).
Starting with the highest severity level, the severity levels supported in Dynatrace are:
- Availability events: Indicate a severe incident within your environment, such as a complete outage or unavailability of servers or processes. These event types have the highest severity level.
- Error events: Inform you of increased error rates or other error-related incidents that interfere with the regular operation of your environment.
- Slowdown events: Indicate a decrease of performance in one of your operational services or applications. Slowdown events are less severe than error or availability events. Nevertheless, they inform you of potential issues with the performance of your services.
- Resource events: Indicate resource contention. Typical examples are CPU saturation and memory saturation events.
- Custom alerts: Custom alerts and severity levels 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 the AI, although they are automatically alerted on.
- Info events: Indicate manually triggered events that don't result in the creation of a new problem. These events are used to mark important deployments or configuration changes as well as administrative events such as the 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.