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
Interesting! I don't know what a good solution is here tbh.
The "easiest" way to fix this would be to clear the registry on reload, but I think that would be very very disruptive. OTOH, we can't really predict from the mappings alone which metrics need clearing. Maybe we would need to defer this decision until a sample is ingested into a metric with conflicting bucket configuration, but then that would un-align metric resets 🤔
One team mate came up with a solution that whenever there is a hot-reload of the configuration we delete all metrics that are configured in the mapping file from the registry (for us, that is disruptive, but acceptable). We are going to test that and come back with results. Would the repo be interested in such solution?
Bug description
What is happening?
This is happening because the metric is never deleted after the reload from the
Registry
.What you expected to happen?
On step
5.
I would expect the new bucket configuration to take place.Notes
Example config:
The text was updated successfully, but these errors were encountered: