The table provides an overview of the built-in incident rules in the Self-Monitoring and Custom System Profiles.
|Severe||Agent Instrumentation Disabled
Reasons for that include: Collector has performance issues, Agent response time is very slow or has poor instrumentation performance.
|It is not possible to instrument the Agent.||Self-Monitoring & Custom|
|Severe||Agent Capturing Disabled||The Agent did not send updates for an extended period of time and was disabled.||Self-Monitoring|
|Warning||Ambigous Agent Mapping||The Agent could be mapped to several System Profiles.||Self-Monitoring|
|Severe||Continuous transaction recording was cencelled||The server is no longer recording PurePaths to disk, probably due to a problem such as out of disk space or file system error.||Self-Monitoring & Custom|
|Severe||Custom events||When you right-click in a chart dashlet and select Heat Field > Add Custom Events you can mark a Custom time period in the heat field to highlight a maintenance or other event in the chart.||Self-Monitoring & Custom|
|Severe||Collector not connected (unexpected)||Connection to a previously connected Collector was lost.
This incident also appears in the Start Center.
|Warning||Conflicting Agent JVM Options||Raises incidents for conflicting JVM options||Self-Monitoring|
|Warning||Dynatrace Server Offline||Signals normal termination of Dynatrace Server.||Self-Monitoring|
|Severe||Dynatrace Server Offline (unexpected)||Signals normal termination of Dynatrace Server.||Self-Monitoring|
|Informational||AppMon Server Online||Signals abnormal termination of Dynatrace Server.||Self-Monitoring|
|Severe||File Session Management||Session storage-related incidents. For example, disk quota exceeded or corrupted sessions detected.||Self-Monitoring|
|Severe||License||License-related incidents, such as an expiring license.
This incident also appears in the Start Center.
|Severe||Low Collector Memory||Agent-related incidents caused by Collector heap memory, such as the Agent's instrumentation being disabled automatically to free some memory.||Self-Monitoring|
|Severe||Low AppMon Server Memory||Low (non-heap) server memory.||Self-Monitoring|
|Severe||Number of Measures||The number of measures reached the maximum of 300,000, which is likely caused by a misconfigured Business Transaction.||Self-Monitoring|
|Severe||Performance Warehouse||Triggered by Performance Warehouse related events.||Self-Monitoring|
|Severe||Performance Warehouse Offline||Connection to Performance Warehouse could not be established. This incident also appears in the Start Center.||Self-Monitoring|
|Severe||Performance Warehouse - Switching Temp Tables Time||Triggered when the insert and switch procedure of the measurement heap tables lasts longer than the default severe threshold.||Self-Monitoring|
|Severe||Performance Warehouse - Writing Measurements Time||Writing of measurements into heap tables takes longer than the severe threshold.||Self-Monitoring|
|Warning||Performance Warehouse - Writing Measurements Time||Writing of measurements into heap tables takes longer than the warning threshold.||Self-Monitoring|
|Severe||Performance Warehouse - Writing Percentiles Time||Writing of percentiles into the percentiles table takes longer than the severe threshold.||Self-Monitoring|
|Warning||Performance Warehouse - Writing Percentiles Time||Writing of percentiles into percentiles tables takes longer than the warning threshold||Self-Monitoring|
|Severe||Port Conflict||A port used for communication on the AppMon Server could not be opened.||Self-Monitoring|
|Informational||Repository Clean-Up||Triggered when writing time is slow.||Self-Monitoring|
|Warning||Scheduled Task Execution Failed||A scheduled task has failed.||Self-Monitoring|
|Informational||System Profile Changed||The system profile configuration has been changed.||Custom|
|Informational||Agent Connected||Raises incidents for individual connected agents.||Custom|
|Informational||Agent CPU Time Capturing||The Agent disabled CPU time capturing because overhead was too high. Adjust the capturing options in the Agent Group's Sensor configuration.||Custom|
|Informational||Agent Hot Sensor Placement||Triggered when the Agent is Hot Sensor placed.||Custom|
|Severe||Application Process Out-of-memory||Memory snapshot triggers, unless it is disabled in the Advanced Settings of the Agent Group mapping.||Custom|
|Severe||Application Process Unavailable (unexpected)||A previously connected application process was shut down.||Custom|
|Severe||Continuous Transaction Recording was cancelled||Custom|
|Warning||Corrupted PurePath(s)||Raises incidents for PurePaths that are corrupted.||Self-Monitoring & Custom|
|Warning||High CPU Usage for Application Process||High CPU usage detected for a longer period.||Custom|
|Warning||High GC Activity for Application Process||A large amount of process time used for garbage collection.||Custom|
|Warning||High Memory Usage for Application Process||Memory usage is at a high percentage for a long time period.||Custom|
|Severe||High Overall Failed User Action Rate||The user action rate exceeds the configured threshold.||Custom|
|Severe||High Overall Failed Transaction Rate||The failed transaction rate exceeds the configured threshold.||Custom|
|Severe||Response Time Degraded for Slow Requests||The response time of slow transactions has changed.||Custom|
|Informational||Session Cleared||Clear Session was executed.||Custom|
|Informational||Test Violation||The test result has changed significantly: degraded, improved, failed, or is volatile.||Custom|
|Warning||Timed Out PurePath(s)||Either a method has not returned or a whole child path did not finish within a certain time.||Custom|
|Warning||Truncated PurePath(s)||PurePath(s) have been truncated because their size exceeds the node limit.||Custom|