Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One common use case I've run into while using Prometheus at Tinder is having a label for success/failure on a single metric, like the following:
With the original code, it seemed like there wasn't a very clean way to handle this; the only way we had solved the problem before was by creating two timers (eg, a
successTimer
and anerrorTimer
) and only ever calling one of the timers later, but that seems both prone to error and not very memory-safe.In addition, we might also want to do something with more than just 2 options, such as tracking average response times for every HTTP code we have in an application. In this case, the multiple-timer approach is also not very scalable, since we'd have to add an additional timer for each new code we wanted to send.
This was the approach I came up with; let me know if there's a better way of handling these kinds of use cases.