Possible to disable check from running?

Sensu Classic (EOL)
1

In the sensu check definition, it’s possible to set

"handle": false

so that when the check runs, the sensu server does not apply any of the normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there any true/false setting that can enable/disable the check itself from running?

Thanks!

-Travis

2

I'm not aware of a setting. If it is standalone you would have to
remove the definition.
If it is publish/subscribe you could set the subscribers to an empty
array, or remove the definition.

···

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear <travis.bear@gmail.com> wrote:

In the sensu check definition, it's possible to set

"handle": false

so that when the check runs, the sensu server does not apply any of the
normal handler logic. (See http://sensuapp.org/docs/0.14/checks\). Is there
any true/false setting that can enable/disable the check itself from
running?

Thanks!

-Travis

3

There is “subdue”, allowing you to suppress executions or notifications for a window, with exceptions.

···

On Nov 3, 2014 8:50 PM, “Kyle Anderson” kyle@xkyle.com wrote:

I’m not aware of a setting. If it is standalone you would have to

remove the definition.

If it is publish/subscribe you could set the subscribers to an empty

array, or remove the definition.

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear travis.bear@gmail.com wrote:

In the sensu check definition, it’s possible to set

“handle”: false

so that when the check runs, the sensu server does not apply any of the

normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there

any true/false setting that can enable/disable the check itself from

running?

Thanks!

-Travis

4

Thanks guys.

The documentation on “subdue” (http://sensuapp.org/docs/0.11/checks) implies that it suppresses handler execution on the server side, rather than check execution on the client side, which is what I’m going for. I’d been hoping for a simple config option, but I’ve scripted up some stuff in Chef to delete the check definition and restart the Sensu client, which seems to do the trick.

-Travis

···

On Monday, November 3, 2014 8:57:11 PM UTC-8, portertech wrote:

There is “subdue”, allowing you to suppress executions or notifications for a window, with exceptions.

On Nov 3, 2014 8:50 PM, “Kyle Anderson” ky...@xkyle.com wrote:

I’m not aware of a setting. If it is standalone you would have to

remove the definition.

If it is publish/subscribe you could set the subscribers to an empty

array, or remove the definition.

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear travi...@gmail.com wrote:

In the sensu check definition, it’s possible to set

“handle”: false

so that when the check runs, the sensu server does not apply any of the

normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there

any true/false setting that can enable/disable the check itself from

running?

Thanks!

-Travis

5

Subdue “at”: “publisher”.

···

On Nov 4, 2014 8:19 AM, “Travis Bear” travis.bear@gmail.com wrote:

Thanks guys.

The documentation on “subdue” (http://sensuapp.org/docs/0.11/checks) implies that it suppresses handler execution on the server side, rather than check execution on the client side, which is what I’m going for. I’d been hoping for a simple config option, but I’ve scripted up some stuff in Chef to delete the check definition and restart the Sensu client, which seems to do the trick.

-Travis

On Monday, November 3, 2014 8:57:11 PM UTC-8, portertech wrote:

There is “subdue”, allowing you to suppress executions or notifications for a window, with exceptions.

On Nov 3, 2014 8:50 PM, “Kyle Anderson” ky...@xkyle.com wrote:

I’m not aware of a setting. If it is standalone you would have to

remove the definition.

If it is publish/subscribe you could set the subscribers to an empty

array, or remove the definition.

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear travi...@gmail.com wrote:

In the sensu check definition, it’s possible to set

“handle”: false

so that when the check runs, the sensu server does not apply any of the

normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there

any true/false setting that can enable/disable the check itself from

running?

Thanks!

-Travis

6

I’m using “handle”: false and the behavior is different than what the doc says. In my case, i don’t see the check even getting published. Using sensu version 0.17.2-1

···

On Tuesday, November 4, 2014 at 10:32:45 PM UTC+5:30, Sean Porter wrote:

Subdue “at”: “publisher”.

On Nov 4, 2014 8:19 AM, “Travis Bear” travi...@gmail.com wrote:

Thanks guys.

The documentation on “subdue” (http://sensuapp.org/docs/0.11/checks) implies that it suppresses handler execution on the server side, rather than check execution on the client side, which is what I’m going for. I’d been hoping for a simple config option, but I’ve scripted up some stuff in Chef to delete the check definition and restart the Sensu client, which seems to do the trick.

-Travis

On Monday, November 3, 2014 8:57:11 PM UTC-8, portertech wrote:

There is “subdue”, allowing you to suppress executions or notifications for a window, with exceptions.

On Nov 3, 2014 8:50 PM, “Kyle Anderson” ky...@xkyle.com wrote:

I’m not aware of a setting. If it is standalone you would have to

remove the definition.

If it is publish/subscribe you could set the subscribers to an empty

array, or remove the definition.

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear travi...@gmail.com wrote:

In the sensu check definition, it’s possible to set

“handle”: false

so that when the check runs, the sensu server does not apply any of the

normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there

any true/false setting that can enable/disable the check itself from

running?

Thanks!

-Travis

7

the handle:false works fine but the subdue: “at”:“publisher” doesn’t work as expected. I still see the check request being sent by the server and also being executed by the client

···

On Friday, October 9, 2015 at 1:36:48 AM UTC+5:30, Akshay Kapoor wrote:

I’m using “handle”: false and the behavior is different than what the doc says. In my case, i don’t see the check even getting published. Using sensu version 0.17.2-1

On Tuesday, November 4, 2014 at 10:32:45 PM UTC+5:30, Sean Porter wrote:

Subdue “at”: “publisher”.

On Nov 4, 2014 8:19 AM, “Travis Bear” travi...@gmail.com wrote:

Thanks guys.

The documentation on “subdue” (http://sensuapp.org/docs/0.11/checks) implies that it suppresses handler execution on the server side, rather than check execution on the client side, which is what I’m going for. I’d been hoping for a simple config option, but I’ve scripted up some stuff in Chef to delete the check definition and restart the Sensu client, which seems to do the trick.

-Travis

On Monday, November 3, 2014 8:57:11 PM UTC-8, portertech wrote:

There is “subdue”, allowing you to suppress executions or notifications for a window, with exceptions.

On Nov 3, 2014 8:50 PM, “Kyle Anderson” ky...@xkyle.com wrote:

I’m not aware of a setting. If it is standalone you would have to

remove the definition.

If it is publish/subscribe you could set the subscribers to an empty

array, or remove the definition.

On Mon, Nov 3, 2014 at 11:04 AM, Travis Bear travi...@gmail.com wrote:

In the sensu check definition, it’s possible to set

“handle”: false

so that when the check runs, the sensu server does not apply any of the

normal handler logic. (See http://sensuapp.org/docs/0.14/checks). Is there

any true/false setting that can enable/disable the check itself from

running?

Thanks!

-Travis