Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reintroduce fallback for scraping schedule? #477

Closed
brandonh-msft opened this issue Mar 29, 2019 · 3 comments
Closed

Reintroduce fallback for scraping schedule? #477

brandonh-msft opened this issue Mar 29, 2019 · 3 comments
Assignees
Labels
configuration All issues related to configuration discussion

Comments

@brandonh-msft
Copy link
Contributor

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)

cc @tomkerkhove for his input

@brandonh-msft brandonh-msft added question Further information is requested configuration All issues related to configuration labels Mar 29, 2019
@brandonh-msft brandonh-msft self-assigned this Mar 29, 2019
@tomkerkhove tomkerkhove added discussion and removed question Further information is requested labels Apr 3, 2019
@tomkerkhove
Copy link
Owner

Thanks for the follow-up on it @brandonh-msft.

Personally, I would suggest to keep it as is because it's more explicit in the scraping schedule rather than the optional approach.

What do you think?

@brandonh-msft
Copy link
Contributor Author

I'm inclined to agree; was just a breaking change @lee0c encountered while doing the helm work. wanted to make sure it was addressed

@tomkerkhove
Copy link
Owner

No problem, thanks for doing that and happy we have an agreement!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration All issues related to configuration discussion
Projects
None yet
Development

No branches or pull requests

2 participants