Family{C}: Generalize labeling specification #7
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.
This patch changes how label names and label values can be passed to the constructor
Prometheus.Family{C}
andPrometheus.labels
. In particular, the label names are now stored as symbols internally. This enables usinggetfield
when creating the corresponding label values. Concretely this enables using e.g. named tuples, and custom structs, as label names/values.For example, the following now works
In this example, the field names of the type,
RequestLabels
, are used as label names in theFamily{C}
constructor. When extracting the counter for a specific set of labels an instance of the struct is used. All non-string values are stringified using string (status_code::Int
in the example above, for example).