List of questions
Related questions
Question 35 - 300-910 discussion
A DevOps engineer is supporting a containerized application with multiple components running across the Kubernetes cluster. Metrics from the container (CPU and memory) and application (requests per second and heap size) are being collected by Prometheus and displayed with Grafan a. Users report transaction timeout problems with the application, but the metric graphs all look within normal levels.
Which type of failure would prevent the engineer from seeing the problem using the captured metrics?
Grafana has lost connectivity to Prometheus, which causes graphs to display only the cached data.
CPU and memory metrics from Kubernetes nodes are not accurate due to the way that containers share resources.
Some containers are crashing regularly and being restarted automatically by Kubernetes.
The metricbeat agent has crashed and is no longer sending new data to Prometheus, so the metrics are not updating.
0 comments
Leave a comment first