Name: Database Monitoring in Dynatrace for SAP Commerce Cloud
Uploaded: 2023-5-8
Duration: 216 s
Description: This video demonstrates the Databases workspace in Dynatrace for SAP Commerce Cloud, and provides useful information on how to monitor it.

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div>This video demonstrates the Databases workspace in Dynatrace for SAP Commerce Cloud, and provides useful information on how to monitor it.</div></div></div>

Database Monitoring in Dynatrace for SAP Commerce Cloud

Hello! Let’s take a look into, the Databases workspace in Dynatrace.  There is no special setup or configuration required, to monitor the database activities in SAP Commerce Cloud.  Database calls are monitored automatically.  By monitoring such calls,  Dynatrace provides insight into various, aspects of database performance, and is even able to deliver automatic, root-cause analysis for performance problems.  Select Databases under Applications & Microservices, to open the Databases page, and see all database instances, that were active within the selected timeframe.  Dynatrace monitors the response time,  failure rate,  throughput,  and every database statement, executed by the Commerce cloud applications.  Select any of the database instances, to see the database service overview page.  The infographics on the database service overview page, provide insight into various aspects of database performance,  including SQL queries or procedures,  SQL modifications,  SQL transactions,  any detected problems or availability issues, hotspots, and more.  The exact list of included tiles depends, on the database technology you're monitoring.  Each tile contains Response time,  Failure rate, and Throughput metrics.  To analyze the individual statements, select View database statements.  All database statements executed during the selected, timeframe are listed in the # database statements section, at the bottom of the Details page.  By default, database statements are, sorted based on median response time.  The list can be sorted by total time,  response time, or slowest 10%,  and you can filter it on statement, database name, vendor, process, or hostname.  Select any statement to view the full details of that statement.  For each statement, Dynatrace shows the number of Executions per minute,  Total executions, Total time, Response time median, and slowest 10% of executions, and Failure rate.   The Backtrace page provides details on the clicks, that triggered the selected execution of the SQL statement,  and it allows you to see which chain of services, and which code leads to a particular SQL statement.  To understand the response time distribution of the SQL command,  select Analyze outliers on the Details page.  The Response time distribution page shows, the number of requests that fell within various response time ranges.  Select any column in the chart to analyze the specific requests,  that fell within that specific response time range.  This enables you to see if certain SQL statements are called frequently, and contribute relatively much more to the response time.  On the database service overview page,  the Current hotspots section offers a quick view of the problem,  highlighting the SQL statement with the highest failure rate.  By selecting a statement in this section,  you can directly view the failures tab on its Details page.   From the Analyze menu Drill icon,  select Outliers to understand the spread of response times.  Statement details to understand the evolution of each, individual SQL statement that undergoes, over time along with the average Rows returned count.  Click on Analyze backtrace to see which user, clicks led to the slowest executions of this SQL statement.  That’s it for Databases.  Thank you for watching!