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.

Sign up for GitHub

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

Jump to bottom

not all installations offer metrics API, some don't like to be contacted #89

Open
donsizemore opened this issue Apr 24, 2023 · 1 comment
Open

not all installations offer metrics API, some don't like to be contacted #89

donsizemore opened this issue Apr 24, 2023 · 1 comment

Comments

@donsizemore
Copy link
Collaborator

We have basic exception catching, but if an installation isn't new enough to offer the metrics API or doesn't allow the metrics VM to contact its API endpoint, in the case of a 404 it should log a "remove me from config.json" message, and in the case of a 403 it should additionally... clean up any cached data associated with that hostname?
@pdurbin
Copy link
Member

pdurbin commented Apr 24, 2023

Hmm, maybe we could have some way to detect when an existing installation has been upgraded to be new enough to added to config.json?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pdurbin @donsizemore