Q25

# 3. Pod/Application Layer (Workload Layer)

Q: # 3. Pod/Application Layer (Workload Layer)

* **Container Metrics**: CPU limits/throttling, memory limits (tracking OOMKilled events), and restarts (gathered via **cAdvisor**). * **State Metrics**: Pod phase status (Running, Pending, Failed) and deployment replica status (using **kube-state-metrics**). * **Application Health**: Scraping application-specific HTTP/gRPC `/healthz` endpoints. * **Log Aggregation**: Gathering container stdout/stderr log streams using agents like Fluentbit or Promtail and indexing them in Grafana Loki o

💬Answer

Container Metrics: CPU limits/throttling, memory limits (tracking OOMKilled events), and restarts (gathered via cAdvisor).
State Metrics: Pod phase status (Running, Pending, Failed) and deployment replica status (using kube-state-metrics).
Application Health: Scraping application-specific HTTP/gRPC /healthz endpoints.
Log Aggregation: Gathering container stdout/stderr log streams using agents like Fluentbit or Promtail and indexing them in Grafana Loki or Elasticsearch.

Related Monitoring Questions

View All MonitoringQuestions →

How do you explain the difference between Monitoring and Observability? Are they the same thing?

What are the Four Golden Signals of Monitoring, and why are they critical?

How does the RED methodology help monitor request-driven microservices?

What is the USE methodology, and in what scenarios is it preferred over RED?

Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker

View Portfolio