prometheus-go-code-review

To review Prometheus instrumentation in Go code, analyze metric types, label cardinality, naming conventions, and registration patterns. This ensures metrics collected via the client_golang library are efficient and reliable before code is merged.

Common Prometheus metric issues in Go applications include using inappropriate metric types, high-cardinality labels that degrade performance, non-standard naming conventions, and registering metrics per-request instead of once globally.

Yes, the code review process checks for high-cardinality label issues in Prometheus metrics. It identifies and flags labels that can degrade performance, ensuring efficient metric exposition for Go applications using the client_golang library.

To validate metric types and naming conventions in Go Prometheus instrumentation, review the code to verify that Counter, Gauge, and Histogram types are used appropriately and that metric names adhere to standard conventions.

Yes, you can use this to check metric registration patterns in client_golang. It ensures that Prometheus metrics are registered exactly once and not per-request, preventing runtime errors and ensuring reliable metric exposition.