Hands-On Infrastructure Monitoring with Prometheus

Not using enough matchers to select a time series

Another common pitfall when writing PromQL expressions, whether for dashboarding or alerting, is not using enough matchers to make sure that the returned samples are from the expected time series. It is considered an anti-pattern in the Prometheus community to namespace metric names to applications when the metric in question is not specific to that particular software, and even if it is, there might be cases where naming collisions occur; this is why it is good practice to scope selectors so that job is always explicitly selected when trying to extract information about a particular software. As an example, we can look at the go_goroutines metric, which is collected by the first-party Prometheus ...