You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switch affected metrics from CounterVecs to GaugeVecs and Set() the metric based on the observed value from Cloudflare.
I'm partial to the second option, as the exporter has been observing requests over a time period, rather than request totals. As a result I think Gauges better reflect the data being exposed here.
That said I'm just a single user of the exporter, so it'd be worth discussing here.
EDIT: I should mention I'm happy to raise a PR if the second option is desirable.
With the metric clearing introduced in #177 , metric values are now increasing or decreasing over time. I.E. not behaving like Counters.
Example:
I think there's two options to consider here:
Add()observed Cloudflare values to the Counter metrics, orCounterVecstoGaugeVecsandSet()the metric based on the observed value from Cloudflare.I'm partial to the second option, as the exporter has been observing requests over a time period, rather than request totals. As a result I think
Gaugesbetter reflect the data being exposed here.That said I'm just a single user of the exporter, so it'd be worth discussing here.
EDIT: I should mention I'm happy to raise a PR if the second option is desirable.