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
Some metrics will need a potentially very large set of labels, or even multiple labels. We need to find a good way of storing and accessing those. Emphasis should be on keeping metric updates cheap.
Along with this, the prometheus exporter should keep prometheusgo.Metric objects between iterations and simply call our internal metrics to update them.
The text was updated successfully, but these errors were encountered:
I saw a TODO in the code in prometheus_exporter.go with your name on it. But this doesn't actually seem to be a problem we have in practice. This feels like a solution looking for a problem. Closing for the time being as we don't need an issue to track this until it becomes an actual problem.
Some metrics will need a potentially very large set of labels, or even multiple labels. We need to find a good way of storing and accessing those. Emphasis should be on keeping metric updates cheap.
Along with this, the prometheus exporter should keep
prometheusgo.Metric
objects between iterations and simply call our internal metrics to update them.The text was updated successfully, but these errors were encountered: