Configure measures and incidents in the Self-Monitoring System Profile. For example, you may want to monitor the amount of free heap memory or the number of garbage collections.
You can enable self-monitoring via Settings > Dynatrace Server > Settings > Enable Self-Monitoring.
This page describes the default Server incident rules and provides links to additional information.
|Incident Rule Name||Description||Further Information|
|Agent Instrumentation Disabled||
This incident is raised for each Agent that disables its instrumentation. This may happen in the following cases:
||Set up Agents|
|Ambiguous Agent Mapping||An Agent is mapped to more than one System Profile. The profile used for mapping depends on the alphanumerical order of profiles. This arbitrary order may cause undesired results. It is recommended that you disable superfluous profiles or adapt the Agent’s name or Agent mapping configuration in the affected profiles to guarantee a unique mapping profile.||
Set up Agents
|Collector not Connected (unexpected)||Connection to an AppMon Collector was lost, perhaps because of network problems or an error in the Collector.||Server Administration|
|Conflicting Agent JVM Options||A conflicting Agent was detected in the JVM startup settings.||Set up Agents|
|AppMon Server Offline||The AppMon Server terminated normally.||Set up the AppMon Server|
|AppMon Server Offline (unexpected)||The AppMon Server terminated abnormally.||Set up the AppMon Server|
|File Session Management||An incident occurred related to session storage. For example, the disk quota was exceeded or corrupted sessions were detected.||Performance Warehouse Administration|
|License||An incident occurred related to licensing. For example, an expired license was detected.||Licensing|
|Low Collector Memory||If a Collector runs low on memory, it tries to prevent an Out-Of-Memory exception by first refusing to accept further instrumented Agents and then by disabling instrumentation for already connected Agents. This incident is raised for each Agent that was accepted only in uninstrumented mode and each Agent for which instrumentation was disabled. Recommended solutions are to increase the Collector’s heap size, reduce the number of connected Agents, or reduce the depth of instrumentation per Agent.||Set up Collectors|
|Low AppMon Server Memory||The AppMon Server detected that it is running low on non-heap memory such as the PermSize memory. It is recommended to increase the PermSize settings for the AppMon Server.||Set up the AppMon Server|
|Scheduled Task Execution Failed||The execution of a Plugin failed.||Manage and Develop User Plugins|
|Performance Warehouse||This incident is triggered by events related to the Performance Warehouse.||Performance Warehouse Administration|
|Performance Warehouse Clean-Up (Repository Clean-Up)||This incident is triggered when the Performance Warehouse cleanup task lasts too long.||Performance Warehouse Administration|
|Performance Warehouse Offline||A connection to the Performance Warehouse could not be established.||Performance Warehouse Administration|
|Performance Warehouse - Switching Temp Tables||This incident is triggered when the time required for switching the temp tables is violated.||Performance Warehouse Administration|
|Performance Warehouse - Writing Measurements/Percentiles Time||These incidents are triggered if the writing task for the repository exceeded either its warning or severe threshold. Review the Performance Warehouse Write Health dashboards for details.||Performance Warehouse Administration|
|Performance Warehouse Event Summary||An incident occurs after the cleanup job if either an important event or an exception occurs during a Performance Warehouse operation.||Performance Warehouse Administration|