Name: Profiling in Dynatrace for SAP Commerce Cloud
Uploaded: 2023-6-8
Duration: 279 s
Description: This video demonstrates the Profiling feature in Dynatrace, a tool which offers you the capability to analyze metric for manually detecting problems. Under the Profiling feature, you will be able to find useful monitoring tools such as:CPU profilingMemory dumpProcess crash analysis

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><p>This video demonstrates the Profiling feature in Dynatrace, a tool which offers you the capability to analyze metric for manually detecting problems. Under the Profiling feature, you will be able to find useful monitoring tools such as:</p><ul><li>CPU profiling</li><li>Memory dump</li><li>Process crash analysis</li></ul></div></div></div>

Profiling in Dynatrace for SAP Commerce Cloud

Hello, in this video we will check the profiling feature under Applications and Microservices in Dynatrace. Apart from automated problem detection, Dynatrace offers you a set of analysis tools that you can use to manually detect problems. The profiling feature provides you with CPU profiling, memory dump, and process crash analysis. Select Profiling and Optimization under Application and Microservices. Here you can see continuous CPU profiling, memory dumps, and process crashes. Continuous CPU profiling allows you to perform the following enhanced code-level CPU analysis. Gain insights into processors and process group hotspots. Access background activity, service activity, single request executions and specific requests. Breakdown and filter data by code execution, network I.O., disk I.O., lock time and wait times over times. Breakdown and filter data by API over time. View forward stuck traces and hotspots with reverse stuck traces. On the Continuous CPU Profiling page, select a process group that contains the process that you want to analyze, example given Tomcat Axis Storefront. Find the process you want to analyze and in the Actions column, select the corresponding Method Hotspots icon to view the Method Hotspots page. On the Process Method Hotspots page, select the Top APIs tab to access the breakdown of a process. To view the forward stack trace, select the Core Hierarchy tab. Each listed method is stacked with the name and color of the API. Select the Hotspots tab to view the top three hotspots with the reverse stack traces. Dynatrace can store and analyze memory dumps for Java,.NET and Node.JSON based applications. Memory dumps are first stored locally on the disk of the monitored application server machine. One agent can upload the memory dumps automatically to an active gate, which can be used as a long-term storage center for memory dumps. To trigger a memory dump, on the profiling and optimization page, select Memory Dumps. Then select the process you want to analyze and select Trigger Dump to generate a new memory dump. It takes a few minutes to generate a memory dump. The time required varies based on application type. Java applications that have multiple gigabytes of heap memory may take several minutes. Once the memory dump is ready, you can download and view memory dumps. In the case of Java applications, the download provides the memory dump in HPROF format, which can be analyzed using a few methods like Eclipse Memory Analyzer and Visual VM. Processes crash for a multitude of reasons and it's often difficult to understand the root causes that contribute to such crashes. When a monitor process crashes, you'll also see a process crash entry in the events section of each affected process and host page. Select Process Crash Details to view a detailed list of the crashes that occurred during the selected time frame. Here you'll find all details related to why each process crashed. The provided crash details include the execution stack frame that crashed. Some of the crash types are native core dump, java core dump, or abnormal program exit due to an exception. Crash type determines which crash details are available. That's it on profiling. Thank you for watching.