Overview

With SAP Commerce Cloud, Dynatrace comes embedded as part of every subscription, giving you access to a powerful set of tools to analyze and optimize the performance of your site. In this article we cover the useful features of Dynatrace and how you can leverage them to troubleshoot performance issues.

What is Dynatrace

Dynatrace is an APM tool to seamlessly bring together infrastructure, application performance, and digital experience monitoring into an all-in-one, automated solution that’s powered by artificial intelligence. Dynatrace assists in driving performance results by providing development, operations, and business teams with a shared platform. Agents are deployed across all nodes in your SAP Commerce Cloud application, giving you insight into your services, JVM, OS and database.

Dynatrace should not be used for the following:

• Analysis of large logs – Kibana should be used for analyzing your logs. You can also set up alerts for logs as covered in Developing SAP Commerce Cloud Locally.
• End user analytics – if you’re trying to review analytics on how users are experiencing your site (e.g. conversion rates) then you may chose to purchase the Dynatrace Digital Experience Monitoring solution or choose to Implement Google Analytics.
• Synthetic testing – To understand the true responsiveness of your site you can purchase the Dynatrace Digital Experience Monitoring solution or look at integrating other solution providers (e.g. Pingdom, Uptime Robot).
• Understand Service Level Agreement (SLA) metrics

Accessing Dynatrace

Dynatrace can be accessed via the Cloud Portal (https://portal.commerce.ondemand.com/ ). In Cloud Portal, first select your subscription, then select the environment you wish to analyze. On each environment page you will see a “Monitoring” section which has an icon to open up Dynatrace. For more details and other options for accessing Dynatrace, please see this page or watch the following video:

https://enable.cx.sap.com/media/How+to+Access+Dynatrace+-+SAP+Commerce+Cloud/1_5i0xt6zz

Data Retention

Before getting started you should be familiar with the data retention periods for Dynatrace. The SAP service data retention policy allows you to preserve critical information about your system performance, ensuring accurate readings and analysis. The standard Dynatrace data retention policy is as follows (measured in calendar days):

• Code-level data: 10 days
• Service-level data: 14 days

The transactional data storage capacity depends on the type of environment:

• Stage/Development environments: 10 GB
• Production environments: 100 GB

If you exceed this upper storage limit before the time periods expire, the system truncates older data by reducing its granularity to make space until the retention time periods expire. If needed, you can purchase extra storage capacity. Contact Support for more information.

For each time series, the data granularity decreases as the retention period expires: the periods of time for each data chunk get longer, reducing their precision. For example, if your data was originally sampled every 30 seconds, the archived data would start with the data sampled every minute, then every five minutes, then every hour, then every day.
Therefore, the system archives the data as follows:

• 0–14 days: Data recorded every minute
• 15–28 days: Data recorded every five minutes
• 29–400 days: Data recorded every hour
• 401 days–five years: Data recorded every 24 hours

Getting Started

Before proceeding it is recommended to review the features and capabilities in Dynatrace by consulting the Dynatrace section of the product documentation. You should ensure you’re comfortable with:

1. Setting up alerts (link). If you require alerts via email please contact SAP Support.
2. Understanding service flows (link).
3. Viewing existing dashboards and creating your own (link).

Troubleshooting Scenarios

In this section we’ll walk you through some common problems and how you might go about using Dynatrace to find a resolution.

Website feels slow

Option #1

1. Click on the “Diagnostics Tools” option in the sidebar.
2. Select “Top database statements”.
3. Select the time period with the high database load.
4. Find the statement causing high execution and click on the “…” icon.
5. In the popup select “service backtrace” to identify which service executed the query.

Specific Page is Failing

1. Click on the “Transactions and services” option in the sidebar.
2. Select your storefront service.
3. Under the “Requests” section, select either “Response Time” or “Failure Rate” options.
4. In the “Filtered by” box, add a new option for “web request URL” and set the value to your page (e.g. /sale) and look for high response and/or failures.
5. Find the statement causing high execution and click on the “…” icon.
6. In the popup select “service backtrace” to identify which service executed the query.
7. Alternatively in the popup you can select “Method Hotspots” and filter on particular method calls (e.g. “Populator”).