Allow subscription/check pairs in check dependencies filter #713
Conversation
| {{< /highlight >}} | ||
|
|
||
| _WARNING: Specifying a subscription/check pair in the check dependencies filter | ||
| may impact Sensu's performance in large-scale installations._ |
There was a problem hiding this comment.
Is there any way to be more specific here? Ideally by providing rough figures or guidance on when you might want to avoid using this.
There was a problem hiding this comment.
Per sensu/sensu-extensions-check-dependencies#12 I think this starts to be a concern in cases where thousands of entries are being returned by the /events API endpoint.
I've opened sensu/sensu-extensions-check-dependencies#13 as a feature request that may help mitigate the performance impact in such cases.
| @@ -406,12 +406,31 @@ Here's an example of a check definition that will be filtered if a check named ` | |||
| } | |||
| {{< /highlight >}} | |||
|
|
|||
| Or, define a dependency by specifying the subscription and the check. | |||
| Here's an example of a check definition that will be filtered if any check named `mysql` on any client subscribed to the `db-nodes` subscription is already alerting: | |||
There was a problem hiding this comment.
This reads a little oddly to me. How about this?
Here's an example of a check definition that will be filtered if a check named
mysqlis already alerting on any client subscribed to thedb-nodessubscription:
Description
Sensu Core 1.5 includes support for specifying a subscription/check pair in the check dependencies filter.
Motivation and Context
Closes #707
Review Instructions
db-notessubscription example make sense?