terraform-provider-pingdom
A Terraform provider for managing Pingdom HTTP, ping, and TCP checks, teams, and contacts via infrastructure as code.
What is terraform-provider-pingdom?
terraform-provider-pingdom is a Terraform provider that allows users to manage Pingdom monitoring resources—such as HTTP, ping, and TCP checks, teams, and contacts—using Terraform configuration files. It solves the problem of manually configuring Pingdom via its web interface by enabling infrastructure as code practices for monitoring setup.
DevOps engineers, SREs, and infrastructure developers who use Terraform for infrastructure management and need to integrate Pingdom monitoring into their automated workflows.
Developers choose this provider to maintain consistency, version control, and reproducibility in their monitoring configurations, reducing manual errors and streamlining the integration of Pingdom with other infrastructure managed by Terraform.
Overview
No longer maintained: Terraform provider to manage pingdom resources
Use Cases
Best For
- Automating Pingdom check creation for new deployments
- Managing team and contact notifications as code
- Integrating Pingdom monitoring with Terraform-managed infrastructure
- Setting up HTTP and ping checks with custom alert thresholds
- Version controlling monitoring configurations alongside infrastructure code
- Dynamically configuring checks based on other resource outputs (e.g., Heroku hostnames)
Not Ideal For
- Projects requiring support for Pingdom's latest API features beyond v3.1
- Teams needing real-time, ad-hoc monitoring updates outside Terraform state management
- Organizations that depend on actively maintained open-source tools with community support
- Users managing advanced Pingdom check types like DNS, transaction, or real-user monitoring
Pros & Cons
Pros
Seamlessly integrates with Terraform for state management and dependency tracking, allowing Pingdom resources to be defined alongside other infrastructure in HCL files.
Enables infrastructure as code practices for Pingdom checks, teams, and contacts, making configurations version-controlled and reproducible, as outlined in the usage examples.
Supports referencing outputs from other Terraform resources, such as Heroku app hostnames, to dynamically configure checks without hardcoding values.
Allows configuration of alert thresholds, notification intervals, and integration with webhooks or user/team notifications, providing flexible monitoring setups based on the README attributes.
Cons
The README explicitly states the project is no longer maintained, posing risks for bugs, security issues, and lack of updates for new Pingdom features or API changes.
Only supports HTTP, ping, and TCP checks, missing other Pingdom check types like DNS or transaction checks, which restricts comprehensive monitoring coverage.
Relies on Pingdom API v3.1, which may be deprecated or lack newer features, and the provider offers no migration path for future API versions.
The README notes that `sendnotificationwhendown` is ignored when using `integrationids`, creating unclear alert behavior that may require Pingdom support or workarounds.
Frequently Asked Questions
Related Projects
terraform-provider-dominosThe Terraform plugin for the Dominos Pizza provider.
terraform-provider-githubTerraform GitHub provider
terraform-provider-keycloakTerraform provider for Keycloak
terraform-provider-hcloudTerraform Hetzner Cloud provider
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.