A Terraform provider for managing Pingdom HTTP, ping, and TCP checks, teams, and contacts via infrastructure as code.
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.
No longer maintained: Terraform provider to manage pingdom resources
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
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.
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.