Getting handlers to execute irrespective of check output

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan

Hello,

You could have the check plugin produce a non-zero exit status, perhaps >= 3, which would cause every result to translate to an event to be handled. Why not declare the check to be a metric?

Sean.

···

On Thu, Jul 11, 2013 at 12:40 PM, Pawan Ranganatha Rao pavan03@gmail.com wrote:

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }

Hi

I’m looking to integrate Sensu and Flapjack and would want all check output data irrespective of the status to be sent to the handler. Thats why I dont want to declare it as a metric.

I’m using the handler to process the event and write into Redis of Flapjack which picks it up for notification.(I have already succeeded in doing this).

Cheers

Pawan

···

On Thursday, 11 July 2013 15:49:45 UTC-4, portertech wrote:

Hello,

You could have the check plugin produce a non-zero exit status, perhaps >= 3, which would cause every result to translate to an event to be handled. Why not declare the check to be a metric?

Sean.

On Thu, Jul 11, 2013 at 12:40 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }

Declaring a check to be a metric just causes every result to translate to an event, irregardless of the exit status.

···

On Thu, Jul 11, 2013 at 12:55 PM, Pawan Ranganatha Rao pavan03@gmail.com wrote:

Hi

I’m looking to integrate Sensu and Flapjack and would want all check output data irrespective of the status to be sent to the handler. Thats why I dont want to declare it as a metric.

I’m using the handler to process the event and write into Redis of Flapjack which picks it up for notification.(I have already succeeded in doing this).

Cheers

Pawan

On Thursday, 11 July 2013 15:49:45 UTC-4, portertech wrote:

Hello,

You could have the check plugin produce a non-zero exit status, perhaps >= 3, which would cause every result to translate to an event to be handled. Why not declare the check to be a metric?

Sean.

On Thu, Jul 11, 2013 at 12:40 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }

ok thanks… Will having a mutator which changes the exit status of the event output work here in this case?

···

On Thursday, 11 July 2013 15:58:31 UTC-4, portertech wrote:

Declaring a check to be a metric just causes every result to translate to an event, irregardless of the exit status.

On Thu, Jul 11, 2013 at 12:55 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

I’m looking to integrate Sensu and Flapjack and would want all check output data irrespective of the status to be sent to the handler. Thats why I dont want to declare it as a metric.

I’m using the handler to process the event and write into Redis of Flapjack which picks it up for notification.(I have already succeeded in doing this).

Cheers

Pawan

On Thursday, 11 July 2013 15:49:45 UTC-4, portertech wrote:

Hello,

You could have the check plugin produce a non-zero exit status, perhaps >= 3, which would cause every result to translate to an event to be handled. Why not declare the check to be a metric?

Sean.

On Thu, Jul 11, 2013 at 12:40 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }

A mutator will only be called if an event has been created that is being passed to a handler that requires it. Using a mutator will not work in this case, need to mark the check type as “metric”, or we implement an alias that doesn’t imply that it produces structure data.

···

On Thu, Jul 11, 2013 at 1:36 PM, Pawan Ranganatha Rao pavan03@gmail.com wrote:

ok thanks… Will having a mutator which changes the exit status of the event output work here in this case?

On Thursday, 11 July 2013 15:58:31 UTC-4, portertech wrote:

Declaring a check to be a metric just causes every result to translate to an event, irregardless of the exit status.

On Thu, Jul 11, 2013 at 12:55 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

I’m looking to integrate Sensu and Flapjack and would want all check output data irrespective of the status to be sent to the handler. Thats why I dont want to declare it as a metric.

I’m using the handler to process the event and write into Redis of Flapjack which picks it up for notification.(I have already succeeded in doing this).

Cheers

Pawan

On Thursday, 11 July 2013 15:49:45 UTC-4, portertech wrote:

Hello,

You could have the check plugin produce a non-zero exit status, perhaps >= 3, which would cause every result to translate to an event to be handled. Why not declare the check to be a metric?

Sean.

On Thu, Jul 11, 2013 at 12:40 PM, Pawan Ranganatha Rao pav...@gmail.com wrote:

Hi

Is there any way I can get a sensu handler to run irrespective of the check output status and not only when there is a state change?

However, I DO NOT want to declare the check to be a metric.

Can this be done using a mutator by changing the status code of the check output in the event data?

Please advise.

Thanks

Pawan


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }


Cheers,

Sean Porter

{ blog: “http://portertech.ca”, projects: “https://github.com/portertech” }