Name: Monitoring Services in Dynatrace for SAP Commerce Cloud
Uploaded: 2023-7-5
Duration: 586 s
Description: This video demonstrates the Services, a feature under Applications & Microservices in Dynatrace which shows all the running services on the Tomcat application server, and how the Tomcat server's performance is affected by its host.

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><div>This video demonstrates the Services, a feature under Applications & Microservices in Dynatrace which shows all the running services on the Tomcat application server, and how the Tomcat server's performance is affected by its host.</div></div></div></div>

Monitoring Services in Dynatrace for SAP Commerce Cloud

Hello. In this video we'll check the services feature under Applications and microservices in Dynatrace. Services can show you which of your web services is running on your Tomcat application server for example, and how your Tomcat service performance is affected by its host. One can see which individual web page calls which specific web server, the application server that receives the resulting web requests, and where the resulting web request service calls are sent. Select Services under Applications and Microservices to see all the active services within the selected time frame. If you have a large number of services, you can use either the filter by search box on the top or the quick filter fields to narrow down the target services by service type, technology, and tags, etc. For each detected service in the services table, you see the service type icon, service names, response times, failure rate, and request throughput. The service metric values, for example response time and failure rates, can be displayed either as the current values or as values calculated over the selected time frame. Select a service like accelerator storefront to see the service detail page. Dynatrace automatically detects and names server-side services of the Commerce Cloud applications based on basic properties of the application deployment and configuration. On the Service Detail page, you see that the last service call happened five minutes ago. Expand the Properties and Tags section. You see the tags attached to the service along with the auto-detected properties like service name, service type, process technology, web context route, and the Kubernetes properties. In the service infographics section you see three columns. The middle column is the current service we're looking at. The left side is the calling entities like services and network clients. The right side is the called entities like services and databases. On the current service tile you see the service throughput is 88 requests per minute. The number of service instances are 2. To bring up all the processes and hosts running the current service, select the current service tile in the middle column. If you select the calling service tile on the left side, you see the Apache web server service is sending web requests to the current Apache Tomcat service. Likewise, you can see which network client or HTTP Synthetic Monitor is sending web requests to the current Tomcat service. And if you select the called service tile on the right side, you see that the solar and database services are being called by the current Tomcat service. Under the service infographic is the dynamic web requests section, where you see the current median response time, failure rate, CPU consumption per request, and the service throughput. Select any of the tiles like response time or the view dynamic requests button under the tiles to see the service details page, which automatically applies the request type filter. In the details section, you see bar charts for various metrics in multiple tabs. The first tab shows response time charts. On the timeline, you can see the median service response time, the number of service requests, the service response time across multiple service instances, that is the fastest and slowest response time at specific times. Below the response time tab, you can switch from the default median view to the slowest 10% and 5% view. To move, expand or shrink the sliding window on the chart and create analysis view. You can click anywhere on the timeline or use the toolbar at the top left corner of the chart. Change the analysis range to 12 hours, 24 hours, or 72 hours in the drop down right under the charts. Once the analysis range is specified, you can click on the analysis buttons to view response hotspots or analyze outliers. By understanding the distribution of the response times across all requests, you can focus on those requests that have the slowest response times. Outlier response times are those requests that have either unusually high or unusually low response times, which greatly affect the overall response time of transactions. Click on the More button to see other analysis tools like Vue Method Hotspots and Vue Service Flow, etc. On the Failure Rate tab, you see the number of service requests per minute, the number of failed service requests per minute, and the failure rate at specific times on the timeline. On the CPU tab, you see the number of service requests per minute and the CPU consumption in milliseconds per service request. On the Throughput tab, you see the number of service requests per minute. Expand the two service instances section to see all the service instances in your environment, along with the throughput, CPU consumption, and the contribution to the overall service performance. In commerce cloud applications, some requests are more important than others that need special attention, either because they're a critical measure of the success of the commerce business, for example a login request or a checkout request, or because they provide vital technical functionality that the commerce application relies on. These are the key requests highlighted in the Key Requests section of the Service Overview page. This visibility is particularly valuable for low volume, high importance requests that would otherwise appear at the bottom of the Top Requests section of a Service Overview page. At the bottom of the service overview page are the top service requests along with the CPU consumption, throughput and contribution to the overall service performance. The performance and attributes of each service request can be analyzed in detail. You're not limited to just certain predefined attributes. You can also configure custom request attributes that you can use to improve filtering and analysis of web requests. On the Request Attributes tab, you see the request attributes, like add to cart, page controller, number of search results, and are essentially key or value pairs that are associated with a particular service request. Back to the service overview page, on the right side of the main screen you see the number of detected problems for the current service during the selected time frame. The current hotspot section allows you to see top hotspot findings of the service, for example requests with slow response time or high failure rate or high CPU consumption. The pane also displays requests with high consumption of request resources. The percentage shows the share of the request in the overall response time of the service. Response time hotspots indicates which activities are consuming the most time for each service. Selecting each of the hotspots issue takes you to the service detail page. The understand dependencies section provides you with various tracing tools to understand the inter-service dependencies and how various business flows work in the application. The Service Flow tool allows you to understand the commerce applications transactions from end to end, which illustrates the sequence of service calls that are triggered by each service request in your environment. With Service Flow you see the flow of service calls from the perspective of a single service or request. Along with the specific services that are triggered, you can also see how each component of a request contributes to the overall response time. The service backtrace tool allows you to know the sequence of service calls that lead up to each request, all the way back up to the browser click that triggered the sequence of calls. For example, you're analyzing a SQL database service and you want to understand the sequence of preceding service requests that ultimately triggered the incoming request to the SQL database. With service level backtrace, you can learn that the SQL database service might be called by the API service, while the API service is called by the node.js service, which in turn was triggered by a click on the add to cart button on a Spartacus storefront. The Distributed Traces tool combines distributed tracing with code level visibility, topology information and metadata to provide the highest level of data granularity and fidelity. One agent automatically captures distributed traces across the entire transaction, spanning multiple devices, operating systems, page actions, and code methods. The events section shows what happened to the current service in the selected timeframe. In this case, the process memory dump event was triggered along with some process restarts. That's all for services. Thanks for watching.