An application currently exposes separate metrics named `http_responses_200_total` and `http_responses_500_total`. Which redesign follows Prometheus guidance best?

AReplace them with one metric such as http_responses_total and a code label

BKeep separate metrics and combine them only in dashboards

CEncode the status code into the job label

DCreate one metric per status family and aggregate manually

Related Questions

A mentor explains that Prometheus distinguishes one time series from another even when both use the ...

easy

A team runs four identical API processes on four scrapeable endpoints. In Prometheus terminology, wh...

easy

A service starts adding the label `environment='prod'` to a metric that previously had no `environme...

medium

An SRE wants a monitoring system that still gives useful answers during an outage even if remote sto...

medium

A finance team asks whether Prometheus should be the source of truth for exact per-request billing. ...

medium

View all Observability Concepts questions

Educational Content — CertQnA practice questions are written against official exam objectives, covering the same domains tested on the real exam. All content is original and independent — not actual exam questions, not affiliated with any certification vendor. Learn more about our content policy

Discussion

Be the first to share your understanding of this concept

⚠️ Discussion is for concept clarification only. Do not share or request actual exam questions or answers.

An application currently exposes separate metrics named http_responses_200_total and http_responses_500_total. Which redesign follows Prometheus guidance best?

Related Questions

Discussion

An application currently exposes separate metrics named `http_responses_200_total` and `http_responses_500_total`. Which redesign follows Prometheus guidance best?