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
@SuperQ we are quite close to a single deployment design where we pass filter params to the scrape endpoint.
However, when using this approach the innerHandler registers process scoped metrics (e.g: stackdriver_monitoring_api_calls_total) with the throwaway registry. These are not globally cumulative and they get reset with each scrape.
We would need these to be globally cumulative and (preferably only) available with the process metrics.
What do you think of these changes ?
I have time to work on this this week.
RFC:
Should the stackdriver scrape endpoint still include these metrics ? If not this is a breaking change.
The text was updated successfully, but these errors were encountered:
Context in #173.
@SuperQ we are quite close to a single deployment design where we pass filter params to the scrape endpoint.
However, when using this approach the
innerHandler
registers process scoped metrics (e.g:stackdriver_monitoring_api_calls_total
) with the throwawayregistry
. These are not globally cumulative and they get reset with each scrape.We would need these to be globally cumulative and (preferably only) available with the process metrics.
What do you think of these changes ?
I have time to work on this this week.
RFC:
The text was updated successfully, but these errors were encountered: