Why deploy alerting resources with Terraform?
You could create alert rules, contact points, and notification policies manually through the Grafana UI. But that means every update requires a manual step, there’s no audit trail, and you can’t reproduce the configuration consistently across environments.
Terraform solves this by treating alerting resources as infrastructure:
- State management. Terraform tracks what’s deployed. It knows whether to create a new alert rule or update an existing one.
- Plan before apply. Preview exactly what will change before any modification touches your Grafana instance.
- One tool for everything. If your team already uses Terraform for servers, networks, or cloud resources, adding alerting resources to the same workflow is natural.
- Reproducible deployments. The same
terraform applyproduces the same result every time, in every environment. - Audit trail. Every deployment is tied to a Terraform state change, which you can track in version control.
When Terraform is the right choice
In the next milestone, you create a service account token that Terraform uses to authenticate to Grafana.
page 2 of 10