Memory/CPU overhead after installing OneAgent| basic troubleshooting

[akram_elkhangy]

1st Scenario – Deep monitoring is enabled

• Switch the impacted host to Infra-structure only monitoring mode and then restart the impacted process/es.
  https://www.dynatrace.com/support/help/how-to-use-dynatrace/hosts/basic-concepts/get-started-with-in...
  • If this resolved the issue, re-enable full stack monitoring and disable deep monitoring of the suspected process/es by creating custom process monitoring rule
    https://www.dynatrace.com/support/help/shortlink/process-group-monitoring#rules
    • If this resolved the issue, trigger a memory dump/CPU profiling analysis and keep the rule in place as a workaround. Contact support and provide the information on the steps completed. See Last step section below.
      https://www.dynatrace.com/support/help/shortlink/memory-dumps#trigger-memory-dumps
      https://www.dynatrace.com/support/help/shortlink/cpu-analysis
  • If the issue was not resolved, move to scenario 2.

2nd Scenario – Infra-only monitoring is enabled

• Disable Log analytics feature for the impacted host
  https://www.dynatrace.com/support/help/shortlink/log-monitoring-configuration#host-specific-oneagent...
• Disable log content Auto discovery
  https://www.dynatrace.com/support/help/shortlink/log-monitoring-auto-discovery-v2#turn-off-log-autod...
• Trigger memory dump/ CPU profiling analysis

Last step & data preparation

• Raise a support ticket, https://support.dynatrace.com/ , and include the following information:
  • all the troubleshooting steps performed
  • whether issue occurs with full stack or infra-only monitoring
  • if log analytics is enabled or disabled
  • include the impacted entities URL + OneAgent diagnostics archive, https://www.dynatrace.com/support/help/shortlink/oneagent-diagnostics#collect-and-review-locally, in addition to the memory dump/ CPU profiling analysis.
    
    Optional table to fill with the working/non-working scenarios
    
    
    

	Infra-only mode	Full stack mode
Log analytics on	Yes/No	Yes/No
Log analytics off	Yes/No	Yes/No

[AntonioSousa]

@akram_elkhangy,

Thanks, these are great tips!

I would also include the exclusion of noisy exceptions & URLs, that can be done through settings:

[akram_elkhangy]

Hi @AntonioSousa 

Thanks for your input and feedback, 

Yes excluding URLs and unnecessary exceptions would be a helpful step here,  this can be done by navigating to  Settings>> Server-side service monitoring>>