Notification settings

Open Respond → Notifications and choose Settings, the button beside Maintenance windows.

Setting	Default	What it does
`flap_hold`	on	Holds alerts while a monitor flaps. Applies to HTTP monitors, heartbeat (cron) monitors and browser checks. HTTP monitors can have their own override.
`outage_ack_stops_repeats`	on	When someone acknowledges an outage, its repeat alerts (`resend_every_minutes`) stop. When off, an acknowledgment only records who is on it.

Hold alerts while flapping

A monitor flaps when it keeps changing status. With flap hold on, Site Qwality sends one Flapping notice, holds each short outage and drops it together with its recovery if the monitor comes back within 5 minutes. Confirm recoveries and hold flapping alerts has the exact thresholds and what each channel receives.

Per-monitor override

Each HTTP monitor can follow the account setting or override it. In the monitor form, the Hold alerts while flapping field is a choice:

Choice	`flap_hold_override`	Result
Follow the Notifications setting	`null`	The monitor does what the account setting says.
Always hold	`true`	The monitor holds flaps even when the account setting is off.
Never hold	`false`	The monitor never holds flaps, even when the account setting is on.

The monitor’s sidebar shows the value in effect and whether it comes from the account.

Acknowledge stops repeats

A notification group with resend_every_minutes repeats the down alert until the monitor recovers. With outage_ack_stops_repeats on, acknowledging the outage ends the repeats; the recovery alert is still sent. With it off, the repeats continue until the monitor recovers.

API

curl https://api.siteqwality.com/account/notification_settings \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY"

{
  "flap_hold": true,
  "outage_ack_stops_repeats": true,
  "updated_at": null,
  "updated_by_user_id": null,
  "updated_by_name": null
}

updated_at is an rfc3339 timestamp, or null while the account has never saved the settings. updated_by_user_id and updated_by_name name whoever saved them last, or are null.

PUT /account/notification_settings takes either field or both; a field you leave out stays as it is. It returns the same shape as the read.

curl -X PUT https://api.siteqwality.com/account/notification_settings \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "flap_hold": false }'

Changing the settings needs the same role as editing notification groups.

Monitor fields

HTTP monitor responses carry two fields:

Field	Type	Description
`flap_hold`	bool	The value in effect: the override when there is one, otherwise the account setting. Read-only.
`flap_hold_override`	bool \| null	The monitor’s own choice. `null` follows the account.

POST /http/job and PUT /http/job/{job_id} accept flap_hold_override. On update, leaving it out keeps the current value and sending null returns the monitor to following the account. Sending flap_hold instead also sets the override.

Audit

Changes appear in the configuration audit with the settings before and after.