Oracle CloudStatic-verified

Alarms that Reach a Person who Confirmed They Want Them

An email subscription delivers nothing until somebody clicks its confirmation link, and until then every alarm publishes to a subscriber who is not there; repeat_notification_duration is null by default, so an alarm fires once at 3am and is never mentioned again. Creates the topic, subscriptions and alarms together, repeats while firing, and lists the subscriptions still waiting on a click.

terraformOracle Cloudoci

Compare Monitoring & Observability across clouds →

oci-monitoring-alarmsvizier v1.2.0

Verification

Static-verified

Passed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan tests (mocked: validation rules · outputs)

Provenance

  • SHA-256 checksum
  • Signature (pending)

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-09-14 · how we verify

Use it from the registry

terraform · opentofu
module "monitoring_alarms" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-monitoring-alarms/oci"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads static-verified because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: static-verified](https://www.iac-bazaar.com/api/artifacts/oci-monitoring-alarms/badge)](https://www.iac-bazaar.com/catalog/oci-monitoring-alarms?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, static-verified on IaC Bazaar: [Alarms that Reach a Person who Confirmed They Want Them](https://www.iac-bazaar.com/catalog/oci-monitoring-alarms?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "monitoring_alarms" {
  source  = "www.iac-bazaar.com/iac-bazaar/oci-monitoring-alarms/oci"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: static-verified

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

oci-monitoring-alarms

Alarms whose notifications reach a person who has confirmed they want them. Works with Terraform and OpenTofu (>= 1.6), oci provider >= 8.0, < 9.0.

An email subscription delivers nothing until somebody clicks the confirmation link. Creating it sends the email; until the link is clicked the subscription sits in PENDING and every alarm that fires publishes to a subscriber who is not there. This module cannot click it; subscriptions_needing_confirmation lists the ones waiting.

An alarm with is_enabled = false evaluates nothing. Created enabled; disabled needs accept_disabled_alarms.

An alarm that notifies once fires at 3am and is never mentioned again. repeat_notification_duration is null by default in the API. Every alarm here repeats hourly while firing unless accept_notify_once.

The topic is the destination. An alarm pointed at a topic with no subscriptions fires into an empty room; refused without accept_topic_without_subscribers.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage

Related modules

Static validatedLive test pending

oci-service-connector

OCI Logging keeps a log for at most six months; a service connector from a log group to Object Storage is the archive, and it can be created INACTIVE, which is how one that was set up has moved nothing since. Created active, reads a whole log group so new logs are included, writes to a bucket, stream, function, topic, metric or Log Analytics, and exports the IAM statement the hub needs.

View module
Static validatedLive test pending

oci-audit

Audit retention set to the 365-day ceiling OCI allows, plus the archive for everything past it: a private bucket with a retention rule (seven years by default, lockable by a date you pass), the service connector that streams every compartment's audit events into it, and the IAM policy without which the connector sits in FAILED. Your Vault key, or the Oracle-managed one by name.

View module
Static validatedLive test pending

oci-logging

Every OCI service log is off until somebody turns it on: a VCN records no flow log, a load balancer no access log, a bucket no read log. Each log here is one service, one resource, one category, created enabled; a log created with is_enabled = false appears in the list and records nothing, and has to be accepted by name. Retention is 30 days by default and the shortest is reported.

View module
Static validatedLive test pending

oci-health-checks

A monitor can be created disabled and probes nothing; one vantage point reports the site down when that location is; and a monitor is a metric, not an alarm - nothing pages until Monitoring reads it. Enabled monitors over HTTPS from three regions by default, and the MQL query each one needs in an alarm exported for the oci-monitoring-alarms module.

View module
Static validatedLive test pending

oci-vcn-flow-logs

VCN flow logs for the subnets you list, since OCI logs per subnet and a subnet added later has none: a log per subnet in a log group created or given, category all rather than reject, ninety days of retention rather than the thirty-day default, and the subnet map as the list to update. Flow logs are the largest log in a tenancy; the map is also the bill.

View module
Static validatedLive test pending

do-monitoring

An alert policy with no email and no Slack webhook is valid, evaluated and triggers to nobody; CPU, memory and disk metrics exist only where the agent runs; and an uptime check without its alert resource is a status page. A recipient required, CPU/memory/disk defaults by tag, the agent-dependent alerts listed, and a down alert plus optional latency and certificate-expiry alerts on every check.

View module