FAQ | This is a LIVE service | Changelog

Skip to content
Snippets Groups Projects
Commit 58e290d4 authored by Monty Dawson's avatar Monty Dawson :coffee:
Browse files

Surface the alerting percentage variable.

parent e13f2107
No related branches found
No related tags found
1 merge request!26Surface the alerting percentage variable.
Pipeline #91723 passed
......@@ -248,9 +248,10 @@ module "uptime_monitoring" {
uptime_check = {
# Accept either e.g. "60s" or 60 for timeout and periods for compatibility
# with previous releases.
timeout = tonumber(trimsuffix(var.alerting_uptime_timeout, "s"))
period = tonumber(trimsuffix(var.alerting_uptime_period, "s"))
path = var.monitoring_path
timeout = tonumber(trimsuffix(var.alerting_uptime_timeout, "s"))
period = tonumber(trimsuffix(var.alerting_uptime_period, "s"))
path = var.monitoring_path
success_threshold_percent = var.alerting_success_threshold_percent
alert_enabled = var.alerting_enabled
}
......
......@@ -122,6 +122,19 @@ variable "alerting_uptime_period" {
description = "Frequency of uptime checks"
}
variable "alerting_success_threshold_percent" {
type = number
default = 75
description = <<EOT
If the percentage of successful uptime checks within the given uptime period falls below
this, an alert will be triggered. Set to 100 to trigger an alert if any uptime check fails,
set to a lower number to tolerate failures without alerting.
Experience has taught us that uptime checks can fail semi-regularly due to transient
problems outside our control, therefore we allow some leeway before triggering an alert.
EOT
}
variable "alerting_enabled" {
type = bool
default = true
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment