-
Notifications
You must be signed in to change notification settings - Fork 5
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
Explore alternatives to Pingdom #54
Comments
I'd be a little hesitant to move to another supplier just because of the lack of Terraform provider: this one for example, seems like a fairly well maintained, featureful community one. That said, if they're as good but maintain their own provider, and we can see a relatively easy migration path, I'd be game. |
That's the provider we're using. It's OK, but has a couple of issues:
To be fair, that provider is being updated, and maybe our best strategy would be to raise PRs for the fixes we'd like to see. I think it's only worth considering moving to a different supplier if we can properly manage everything in code. So, I think it's worth exploring if such a service exists. |
This open-source, github actions-based monitoring system looks interesting, although it lacks the pingdom feature of multiple different points of origin for service checks: |
Requires User Research |
Stale. |
Virtually all teams in the MoJ use Pingdom for uptime monitoring, and alerting via Slack and/or pagerduty.
Pingdom have no official terraform provider, so part of the process of setting up monitoring for services relies on clickops.
Explore alternatives such as StatusCake to try and find something with better support for our preferred infrastructure as code approach.
related to #57
The text was updated successfully, but these errors were encountered: