Issues with DT 5.6.0 Incidents
Hi Team,
The bulit in "application process out of memory" incident in DT 5.6.0 has evaluation time frame of 10 seconds and not allowed to be altered. Can we change it to say 5 minutes or so as we are bombarded with hundreds of emails for an issue. Also it takes dump every 10 seconds for a issue causing numerous of dumps to be taken which could further slow down the application and also fill up the DT sessions directory.
Also have configured CPU utlization and Memory utlization incidents but they do not seem to be working.
Have used the measure Current CPU load( process performance ) for CPU utilization and Memory Utilization ( Java Virtual Machine ) for Memory Utilization but they do not seem to be working.
Can anybody help.
Regards,
Narendra Patel
Hi
The evaluation timeframe cannot be changed for the out-of-the-box measures. It should however not trigger multiple times for the same incident. If this keeps happening you can also deactivate that Incident but I would almost suggest to open a support ticket to figure out why this incident triggeres repeatadly for the same JVM.
The Heap Dump is created in case an out-of-memory exception is thrown. This can be disabled in the Advanced Agent Mapping Settings in your System Profile. In your Agent Group / Tier click on Agent Mapping and there click on Advanced. Uncheck the box "Create memory snapshot ..."
As for you CPU Incidents. Which thresholds did you specify? also - did you verify the values that actually come in on these measure by putting them on a chart? This is always my approach. First I make sure these measures actually return the values I expect. It also allows me to learn which value ranges are reported. Then I add these measures to an incident by specifying a good threshold, aggregation level and evaluation timeframe
Andi
Hi Andreas,
Thank you for your response. Will check the asked things at my end.
Regards,
Narendra Patel
