Q: Prometheus is a pull-based system, meaning it scrapes targets that are continuously running. How do you monitor a cron job that runs for only 3 seconds and terminates before Prometheus has a chance to scrape it?
You use the Prometheus Pushgateway.
Want to master this scenario in a live sandbox? The Linux Foundation's Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Logs tell you what happened, metrics tell you where to look, and distributed traces pinpoint the exact slow component. The interviewer is testing: Pushgateway architecture.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
You use the Prometheus Pushgateway. The Pushgateway is an intermediary, continuously running component. The short-lived cron job, right before it terminates, actively *pushes* its final metrics (like job_duration_seconds or items_processed) to the Pushgateway via an HTTP POST. The Pushgateway stores these metrics in memory indefinitely. Prometheus can then leisurely scrape the Pushgateway on its standard interval (e.g., every 15 seconds) to collect the metrics of the dead job.
- Immediate Triage: You use the Prometheus Pushgateway.
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability Prometheus pull High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
- Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability Prometheus pull Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
- Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability Prometheus pull Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
- Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability Prometheus pull Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.