2V0-71.23 Question 302
Single answerYou are managing a Kubernetes environment using VMware Tanzu and have integrated Aria Operations for Applications (formerly Tanzu Observability) to monitor application performance. Developers report performance degradation in a microservice-based application. Upon investigation, you identify high latency in one of the services. Which feature of Aria Operations for Applications should you use to pinpoint the root cause of the issue?
- A
Live Metrics Stream
- B
Distributed Tracing
- C
Synthetic Monitoring
- D
Log Aggregation
Show answer and explanation
Correct answer: B
Explanation
Distributed Tracing in Aria Operations for Applications is the most effective feature for identifying root causes in a distributed system experiencing latency. It visualizes the propagation of requests across the microservices, enabling you to identify which service or operation is causing the performance degradation. Other options, while useful for monitoring and troubleshooting, do not provide the same level of insight into inter-service communication and latency bottlenecks.
- A. Incorrect.
Live Metrics Stream provides real-time metrics for various application components, but it is not specifically designed to trace requests across distributed services, which is essential for identifying latency issues.
- B. Correct.
Distributed Tracing allows you to track requests as they propagate through various services in a distributed system, making it the ideal tool for identifying high-latency services and pinpointing root causes.
- C. Incorrect.
Synthetic Monitoring simulates user interactions to test application availability and performance, but it does not provide insights into real-time issues or trace requests across services.
- D. Incorrect.
Log Aggregation collects and centralizes logs for troubleshooting, which can be helpful but is not as effective as Distributed Tracing in visualizing end-to-end request flows and latency bottlenecks.