Environment incidents

The environment incidents are raised if a possible issue with your AppMon Server configuration or the underlying system is detected.

General incidents

Sizing not supported
  • Reason: Sizing unsupported is configured for the AppMon Server.
  • How to resolve:
  • Only use the unsupported sizing under Dynatrace support advisement.
Different sizing on backend and frontend
  • Reason: The configured sizing of the frontend and backend server does not match.
  • How to resolve:
Physical memory insufficient
  • Reason: The physical memory of your machine does not meet the requirements of the configured sizing, based on deployment sizing).
  • How to resolve:
    1. Provide the AppMon Server with the required physical memory.
    2. Switch to a smaller sizing.
    3. If your AppMon Server runs on a VM such as the VMware vSphere Client, configure the VM appropriately.
CPU core number insufficient
  • Reason: The CPU core number of your machine does not meet the requirements of the configured sizing, based on deployment sizing).
  • How to resolve:
    1. Provide the AppMon Server with a CPU providing the required core number.
    2. Switch to a smaller sizing.
    3. If your AppMon Server runs on a VM such as the VMware vSphere Client, configure the VM appropriately.
CPU frequency insufficient
  • Reason: The CPU frequency of your machine does not meet the requirements of your configured sizing, based on deployment sizing).
  • How to resolve:
    1. Provide the AppMon Server with a CPU providing the required frequency.
    2. Switch to a smaller sizing.
    3. If your AppMon Server runs on a VM such as the VMware vSphere Client, configure the VM appropriately.
Energy saving mode active
  • Reason: The power settings of your OS are not configured to provide the maximum CPU performance.
  • How to resolve:
  • Your BIOS and VM hypervisor settings are not considered by the incident. Please make sure that the energy saving mode is disabled for them as well.

VMware specific incidents

VMware - no CPU MHz reserved
  • Reason: No CPU MHz are reserved for the AppMon Server's VM.
  • How to resolve:
    • Reserve the required CPU MHz for the AppMon Server in the vSphere Client.
VMware - reserved CPU MHz insufficient
  • Reason: There are not enough CPU MHz reserved for the AppMon Server's VM.
  • How to resolve:
    • Reserve the required CPU MHz for the AppMon Server in the vSphere Client.
VMware - CPU MHz limit too low
  • Reason: The configured CPU MHz limit for the VM the AppMon Server is running is too low.
  • How to resolve:
    1. Remove the CPU MHz limit for the VM.
    2. Increase the CPU MHz limit so it is sufficient.
VMware - no memory reserved
  • Reason: No memory is reserved for the for the AppMon Server's VM.
  • How to resolve:
    • Reserve the required memory for the AppMon Server in the vSphere Client.
VMware - reserved memory insufficient
  • Reason: There are not enough memory reserved for the AppMon Server's VM.
  • How to resolve:
    • Reserve the required memory for the AppMon Server in the vSphere Client.
VMware - memory limit too low
  • Reason: The configured memory limit for the VM the AppMon Server is running is too low.
  • How to resolve:
    1. Remove the memory limit for the VM.
    2. Increase the memory limit so it is sufficient.
VMware - memory ballooning
VMware - hypervisor swapping