How sensu produce an event?


#1

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an
event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?


#2

The creation of events are done on the Sensu server.

Sean.

···

On Feb 10, 2015 6:05 PM, “Timothy John” tim_john@126.com wrote:

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?


#3

Thanks Sean

在 2015年2月11日星期三 UTC+8上午10:07:09,Sean Porter写道:

···

The creation of events are done on the Sensu server.

Sean.

On Feb 10, 2015 6:05 PM, “Timothy John” tim_...@126.com wrote:

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?


#4

Hi, Sean. Sorry for ask again. I’ve noticed that the Doc said “transport type handler will publishing event data to a Sensu transport (RabbitMQ default)”, but since events and event data are created on the Sensu server. Why should the event data should be publish to RabbitMQ again?

In my opinion (which might be wrong), according to the architecture picture, clients send check results to RabbitMQ, then RabbitMQ send these results to server, after that, server create events and events data, finally, server send events data to handler. There’s no need for sending events data back to RabbitMQ.

在 2015年2月11日星期三 UTC+8上午10:07:09,Sean Porter写道:

···

The creation of events are done on the Sensu server.

Sean.

On Feb 10, 2015 6:05 PM, “Timothy John” tim_...@126.com wrote:

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?


#5

Transport (type) event handlers are for shipping event data onto the transport for another consumer, eg. Graphite Carbon AMQP consumer.

Sean.

···

On Feb 10, 2015 7:12 PM, “Timothy John” tim_john@126.com wrote:

Hi, Sean. Sorry for ask again. I’ve noticed that the Doc said “transport type handler will publishing event data to a Sensu transport (RabbitMQ default)”, but since events and event data are created on the Sensu server. Why should the event data should be publish to RabbitMQ again?

In my opinion (which might be wrong), according to the architecture picture, clients send check results to RabbitMQ, then RabbitMQ send these results to server, after that, server create events and events data, finally, server send events data to handler. There’s no need for sending events data back to RabbitMQ.

在 2015年2月11日星期三 UTC+8上午10:07:09,Sean Porter写道:

The creation of events are done on the Sensu server.

Sean.

On Feb 10, 2015 6:05 PM, “Timothy John” tim_...@126.com wrote:

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?


#6

So, this RabbitMQ (or other transport) here is actually not the same role in the architecture picture, right?

在 2015年2月11日星期三 UTC+8上午11:15:57,Sean Porter写道:

···

Transport (type) event handlers are for shipping event data onto the transport for another consumer, eg. Graphite Carbon AMQP consumer.

Sean.

On Feb 10, 2015 7:12 PM, “Timothy John” tim_...@126.com wrote:

Hi, Sean. Sorry for ask again. I’ve noticed that the Doc said “transport type handler will publishing event data to a Sensu transport (RabbitMQ default)”, but since events and event data are created on the Sensu server. Why should the event data should be publish to RabbitMQ again?

In my opinion (which might be wrong), according to the architecture picture, clients send check results to RabbitMQ, then RabbitMQ send these results to server, after that, server create events and events data, finally, server send events data to handler. There’s no need for sending events data back to RabbitMQ.

在 2015年2月11日星期三 UTC+8上午10:07:09,Sean Porter写道:

The creation of events are done on the Sensu server.

Sean.

On Feb 10, 2015 6:05 PM, “Timothy John” tim_...@126.com wrote:

In the Sensu Checks page (http://sensuapp.org/docs/0.16/checks) of official documents, it says "by default, only non-zero (exit status > 0) check results produce an event, causing the creation of event data".
I want to know where these processes occur? Is it happens on server or client?