Terraform provider

Define monitors, alert channels, and status pages in HCL and manage them alongside the rest of your infrastructure.

Overview

The Teravor Monitor Terraform provider will land as part of Phase 2. It'll let you define monitors, alert channels, and status pages in HCL and manage them alongside the rest of your infrastructure. Track progress on the roadmap.

What to expect

• Resources for monitors, alert channels, and status pages — schemas mirror the REST API.
• Import existing resources by ID so you can adopt Terraform without recreating.
• API-token auth via a provider block or TERAVOR_API_TOKEN.
• Published to the Terraform Registry under the Teravor namespace.
• Source on GitHub, MIT-licensed, with examples for common topologies.

Example config

This is the expected HCL shape once the provider ships:

terraform {
  required_providers {
    teravor = {
      source  = "teravor/teravor"
      version = "~> 1.0"
    }
  }
}

provider "teravor" {
  # uses TERAVOR_API_TOKEN env var by default
}

resource "teravor_monitor" "api_health" {
  name         = "api.acme.io health"
  type         = "http"
  url          = "https://api.acme.io/healthz"
  interval_sec = 60

  expect {
    status = 200
  }
}

resource "teravor_status_page" "acme" {
  name     = "Acme Status"
  slug     = "acme"
  monitors = [teravor_monitor.api_health.id]
}

Early access

Email [email protected] with a sketch of how you'd use it and we'll loop you in when the beta opens.