Skip to main content

Alert Methods

How do I close an Alert method?​

  • The PagerDuty Alert Method supports an Alert Resolution feature that allows you to send an all-clear notification from Nobl9 signaling that an alert should be marked as resolved in the PagerDuty UI. For details, see PagerDuty Alert | Nobl9 Documentation . For other sources, alerts must be closed manually.

How many custom headers can I include when adding a Webhook as an Alert Method??​

  • The maximum of custom headers is 10.

Is there a way to notify the project members based on their alert preference if there is a new SLO added or removed?​

  • No, not yet. This feature is on our roadmap.

How can I browse my fired Alerts?​

  • The only way to get the log of all fired alerts is through sloctl. To do that, use the sloctl get alerts command.

My PagerDuty alert did not resolve itself after the SLO had gone back to green for a while. Why not?​

  • To enable this feature, you need to check the Send a notification after the cooldown period is over box in the PagerDuty Alert Method wizard or add the optional sendResolution section to your PagerDuty YAML configuration (with a value other than the default of nil). For more details, refer to the PagerDuty Alert | Nobl9 Documentation.

Does the PagerDuty Alert Resolution feature work via Terraform?​

  • No. Our Terraform provider has not been updated to support it.

Let’s say a condition is triggered, and remains triggered. How often will the alert fire?​

  • If the condition remains triggered, the alert will only fire once, and it will stay open. It will be closed after the condition stops being triggered for a period of time, called the cooldown period. After the alert is closed, a new one can be triggered if the condition arises again.
  • For more details about Alert Methods, refer to the Alert Methods | Nobl9 Documentation.