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
Prior to the fix for #259 (merged by PR #473), it was possible to not specify a scraping interval - default or otherwise - for Promitor. However, the PR introduced a change where - at minimum - metricDefaults.scraping.schedule was required in the metrics-declaration.yaml file. This is a change from previous where the PROMITOR_SCRAPING_SCHEDULE environment variable was optional and would fall back to a 5 minute schedule if not specified.
I'm opening this "bug" issue to discuss this change; if it is indeed a bug we can introduce the fallback.
Worth noting that this breaking change necessitated a change to the helm chart (#476)
Prior to the fix for #259 (merged by PR #473), it was possible to not specify a scraping interval - default or otherwise - for Promitor. However, the PR introduced a change where - at minimum -
metricDefaults.scraping.schedule
was required in themetrics-declaration.yaml
file. This is a change from previous where thePROMITOR_SCRAPING_SCHEDULE
environment variable was optional and would fall back to a 5 minute schedule if not specified.I'm opening this "bug" issue to discuss this change; if it is indeed a bug we can introduce the fallback.
Worth noting that this breaking change necessitated a change to the helm chart (#476)
cc @tomkerkhove for his input
The text was updated successfully, but these errors were encountered: