Open brettimus opened 1 year ago
Hey there!
First off, thanks for your work on this. It's nice to see a well-thought-out solution to getting serverless functions' metrics into Prometheus.
I bumped into an issue pushing metrics of this form:
function_calls_total{function="rabbit",objective_name="animalz"} 1 function_calls_total{function="wildRabbit"} 1
As a workaround, I can set the objective_name label to the empty string whenever it does not exist.
objective_name
It seems like under the hood, your https://github.com/sinkingpoint/openmetrics-parser library wants for all metrics to have the same labels. (Maybe I should open an issue there instead?)
It gets mad when one metric has a superset or subset of the other's label names.
According to the Prometheus docs, setting a label to the emptystring is the same as not setting it at all.
So, to me, the expected behavior here is that
would be equivalent to pushing
function_calls_total{function="rabbit",objective_name="animalz"} 1 function_calls_total{function="wildRabbit",objective_name=""} 1
Curious to hear your thoughts!
Interesting. We sort of assume that labelsets don't change, either up or down. Will take a poke at this this weekend
Hey there!
First off, thanks for your work on this. It's nice to see a well-thought-out solution to getting serverless functions' metrics into Prometheus.
I bumped into an issue pushing metrics of this form:
As a workaround, I can set the
objective_name
label to the empty string whenever it does not exist.It seems like under the hood, your https://github.com/sinkingpoint/openmetrics-parser library wants for all metrics to have the same labels. (Maybe I should open an issue there instead?)
It gets mad when one metric has a superset or subset of the other's label names.
According to the Prometheus docs, setting a label to the emptystring is the same as not setting it at all.
So, to me, the expected behavior here is that
would be equivalent to pushing
Curious to hear your thoughts!