Services provides two key perspectives for monitoring your applications: health and performance. In this tutorial, we'll focus on the performance view.
The following video will walk you through the performance view and show you how to drill down into individual services to understand their health, metrics, infrastructure, logs, and events.
This video is slightly outdated. The current
Services app offers additional analysis pages, including failure analysis, response time, database queries, and messaging.
You can try the steps below in the Dynatrace Playground environment.
From
Services, go to Explorer > Performance to view all services along with their health and custom alerts, failure rates, and response times. Hover over a service's failure rate to see the degree of rate increases and quickly identify services that are degrading in performance.
In the Type to filter field, enter k8s.namespace.name = astroshop to display services that relate to the astroshop Kubernetes namespace.
Select the astroshop-recommendation service to open the detail view, which contains several tabs with detailed information about that service.
The Overview tab provides comprehensive charts that show the failure rate, response time, and throughput across all endpoints of the selected service. This gives you a complete picture of how the service is performing. The overview also displays service properties such as the Kubernetes cluster and namespace where the service is deployed, along with other deployment metadata.
Go to the Additional telemetry tab to view custom metrics from various sources, like Spring Micrometer and OpenTelemetry. These non-standard metrics supplement the default performance data with application-specific information that is important to your service.
Switch to the Infrastructure tab to view the pods, processes, and hosts associated with the selected service. With this information, you can understand where the service is running and identify infrastructure dependencies.
Go to the Logs tab to run log line queries and search for warnings, errors, or any log entries within the current timeframe. This makes it easy to correlate performance issues with specific log messages.
Services