Exam Professional Cloud Developer topic 1 question 262 discussion

I go with A

The key part of the question prompting the use of OpenTelemetry over Prometheus is: "Your customers are reporting that your application is running slowly at unpredictable times. The application doesn’t report any metrics." This indicates a need for detailed instrumentation to trace and diagnose performance issues across various external service interactions. OpenTelemetry, with its comprehensive APIs and SDKs for collecting a wide range of telemetry data (traces, metrics, logs), is well-suited for this task. It allows for tracing the application's workflow and identifying bottlenecks, which is essential for understanding the root cause of the inconsistent performance.

OpenTelemetry provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application. You can analyze them using Prometheus, Jaeger, and other observability tools. This will help you understand the performance of your application and identify any bottlenecks or issues causing the slowdown. It’s a comprehensive tool for observability, making it a suitable choice for this scenario.

I go with A. Opentelelmetry standard supports tracing, metrics, logging. With tracing we can find out what is causing the performance issue. Zipkin is almost obsolete now.

I should be A.

OpenTelemetry is a set of APIs, libraries, and agents that help you collect telemetry data (such as traces, metrics, and logs) from your applications. By instrumenting your application with OpenTelemetry, you can gather performance metrics, trace requests across different components, and identify potential bottlenecks or issues causing inconsistent performance.

Managed Service for Prometheus collects metrics from Prometheus exporters and lets you query the data globally using PromQL, meaning that you can keep using any existing Grafana dashboards, PromQL-based alerts, and workflows. It is hybrid- and multi-cloud compatible, can monitor both Kubernetes and VM workloads, retains data for 24 months, and maintains portability by staying compatible with upstream Prometheus. https://cloud.google.com/stackdriver/docs/managed-prometheus

It should be A. https://cloud.google.com/trace/docs/trace-app-latency