According to the documentation, silences can be applied to subscriptions or checks. If a silence is applied to an subscription, a wildcard is provided for the check, and vice versa.
From the Web UI, I can manually create a silence for a specific check and not specify the subscription. The result is that the check is applied to all subscriptions/entities.
For example, if I create a new silence for a check called
check_salt_procs and leave
subscription field blank, I get the following silence:
The API seems to behave differently and I’ve been unable to successfully create the same silence.
If I try to submit my request without a subscription, the backend returns a 400.
If I include the name of the targeted subscription (which is not desirable for this use case), the entry name of the silence becomes the name of the subscription.
For example, if I define subscription in my request as
"subscription": "salts", my silence becomes
Is this type of silence via the API possible? And if so, is there an example of a check silence without a subscription anywhere? The reference examples only appear to cover subscriptions.