The discard notifier discards all notifications. Use it to silence a subset of routes
without deleting them, hold a place in a notification policy while you restructure
routing, or test notification policy behavior without delivering alerts.
You can’t create discard notifiers from within the Chronosphere Observability
Platform interface.
Select from the following methods to create a discard notifier.
To create a discard notifier using Chronoctl:
-
Define the resource definition for your discard notifier:
Replace the following:
NAME: A descriptive name, such as Example discard.
SLUG: A unique identifier, such as example-discard.
-
Apply the changes:
Replace
FILE_NAME with the name of your notifier YAML file.
To create a discard notifier using Terraform:The discard notifier’s Terraform resource type is
chronosphere_blackhole_alert_notifier. “Blackhole” is the internal name for the
discard notifier. There is no chronosphere_discard_* resource.
-
Create a discard notifier with Terraform by using the
chronosphere_blackhole_alert_notifier type followed by a name in a resource
declaration:
-
Run
terraform apply to create the notifier resource.
To complete this action with the Chronosphere API, use the
CreateNotifier
endpoint.Because the Chronosphere API requires authentication, include an API token with your
curl request, as shown in the following example. For more details, see
Create an API token.Replace the following:
TOKEN: Your API token.
INSTANCE: The subdomain name for your organization’s Observability Platform instance.
METHOD: The HTTP method to use with the request, such as GET or POST.
ENDPOINT_PATH: The specific endpoint you want to access.