PCA Exporters & Integrations Flashcards
6 cards from real PCA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 PCA Exporters & Integrations flashcards as text
What is the Prometheus pushgateway used for?
Answer: Accepting metrics pushed by short-lived jobs that cannot be scraped
The Pushgateway is an intermediary that accepts metric pushes from batch jobs or ephemeral processes, holding them until Prometheus scrapes the gateway.
What is a key drawback of using the Prometheus Pushgateway for all metrics?
Answer: Metrics persist after the originating job ends, hiding job failures
Pushed metrics remain in the Pushgateway until explicitly deleted, so a failed or stale job may still appear healthy because its last metrics are still present.
Which Prometheus client library method is used to push metrics to a Pushgateway in the Go client?
Answer: push.New().Push()
The Go client's `push.New(url, job).Collector(c).Push()` chain sends a collector's metrics to the specified Pushgateway URL under the given job name.
What label does the Pushgateway automatically add to all metrics to identify the originating job?
Answer: job
The Pushgateway uses the job name from the push URL path (`/metrics/job/`) as the `job` label on all stored metrics.
What HTTP method should a batch job use to delete its metrics from the Pushgateway after completion?
Answer: DELETE /metrics/job/
Sending an HTTP DELETE to `/metrics/job/` removes the metric group from the Pushgateway, preventing stale data from persisting.
The `statsd_exporter` converts StatsD metrics to Prometheus format using which configuration file feature?
Answer: Mapping rules that translate StatsD metric names to Prometheus labels and names
The statsd_exporter's mapping configuration translates dot-separated StatsD metric names into Prometheus metric names with proper labels using regex-based mapping rules.