sensu

Sensu Classic (EOL)
1

I have the clients subscribe to a group dev, uat, live etc as appropriate. You can then filter appropriately based on what the desired handler should do – ie pager handler only deals with live subscribers.

···

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of dollars.

Thus far, I don’t see an obvious way to do the following

if a production page, send it via both the email handler and pager handler

if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json’s aren’t subdivided generally across dev, qa, uat, stage, production, and infrastructure.

I want something simple so that I don’t have to special-case configure everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don’t want to have to do things like lay out allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all individual *.json’s on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

2

I have the clients subscribe to a group dev, uat, live etc as appropriate. You can then filter appropriately based on what the desired handler should do – ie pager handler only deals with live subscribers.

···

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of dollars.

Thus far, I don’t see an obvious way to do the following

if a production page, send it via both the email handler and pager handler

if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json’s aren’t subdivided generally across dev, qa, uat, stage, production, and infrastructure.

I want something simple so that I don’t have to special-case configure everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don’t want to have to do things like lay out allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all individual *.json’s on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

3

https://sensuapp.org/docs/latest/getting-started-with-filters

···

On Tue, Apr 26, 2016 at 6:38 AM, Stuart Cracraft <smcracraft@me.com> wrote:

Thanks! Can you send an example of a filter to block pages?

Apparently subdue can only subdue from one time to another. I haven't been
able to get it to say block 7pm to 7am PLUS all hours from 7pm Friday to 7am
Sunday for non-prod.

On Apr 26, 2016, at 1:55 AM, Smith Joel (HEALTH AND SOCIAL CARE INFORMATION > CENTRE) <joel.smith1@hscic.gov.uk> wrote:

I have the clients subscribe to a group dev, uat, live etc as appropriate.
You can then filter appropriately based on what the desired handler should
do – ie pager handler only deals with live subscribers.

From: sensu-users@googlegroups.com [mailto:sensu-users@googlegroups.com] On
Behalf Of Stuart Cracraft
Sent: 25 April 2016 19:13
To: sensu-users
Subject: sensu

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of
dollars.

Thus far, I don't see an obvious way to do the following

   if a production page, send it via both the email handler and pager
handler

   if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json's aren't subdivided generally across dev, qa,
uat, stage, production, and infrastructure.

I want something simple so that I don't have to special-case configure
everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don't want to have to do things like lay out
allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all
individual *.json's on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on
schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

********************************************************************************************************************

This message may contain confidential information. If you are not the
intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or
take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS
staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive
information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can be
accessed anywhere

********************************************************************************************************************

4

Not enough practical real-world examples!

···

On Apr 26, 2016, at 7:50 AM, Kyle Anderson <kyle@xkyle.com> wrote:

https://sensuapp.org/docs/latest/getting-started-with-filters

On Tue, Apr 26, 2016 at 6:38 AM, Stuart Cracraft <smcracraft@me.com> wrote:
Thanks! Can you send an example of a filter to block pages?

Apparently subdue can only subdue from one time to another. I haven't been
able to get it to say block 7pm to 7am PLUS all hours from 7pm Friday to 7am
Sunday for non-prod.

On Apr 26, 2016, at 1:55 AM, Smith Joel (HEALTH AND SOCIAL CARE INFORMATION >> CENTRE) <joel.smith1@hscic.gov.uk> wrote:

I have the clients subscribe to a group dev, uat, live etc as appropriate.
You can then filter appropriately based on what the desired handler should
do – ie pager handler only deals with live subscribers.

From: sensu-users@googlegroups.com [mailto:sensu-users@googlegroups.com] On
Behalf Of Stuart Cracraft
Sent: 25 April 2016 19:13
To: sensu-users
Subject: sensu

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of
dollars.

Thus far, I don't see an obvious way to do the following

  if a production page, send it via both the email handler and pager
handler

  if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json's aren't subdivided generally across dev, qa,
uat, stage, production, and infrastructure.

I want something simple so that I don't have to special-case configure
everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don't want to have to do things like lay out
allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all
individual *.json's on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on
schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

********************************************************************************************************************

This message may contain confidential information. If you are not the
intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or
take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS
staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive
information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can be
accessed anywhere

********************************************************************************************************************

5

Subdue allows exceptions which can be expressed as an array of hashes. Could you subdue as follows?:

“begin”: “00:00”,
“end”:“23:59”,
“exceptions”: ``[{“day”:“monday”, “begin”: “07:00”, “end”: “19:00”},{“day”:“tuesday”,"begin": "07:00", "end": "19:00"},{"day":```` "wednesday",“begin”: “07:00”, “end”: “19:00”},{“day”:```` “thursday”,"begin": "07:00", "end": "19:00"},{"day":```` "friday", “begin”: “07:00”, “end”: “19:00”}]``````

``

``

This would subdue all the time except for the times you want it to be active.

Cheers,

Joel

···

On Tuesday, 26 April 2016 14:38:11 UTC+1, Stuart Cracraft wrote:

Thanks! Can you send an example of a filter to block pages?

Apparently subdue can only subdue from one time to another. I haven’t been able to get it to say block 7pm to 7am PLUS all hours from 7pm Friday to 7am Sunday for non-prod.

On Apr 26, 2016, at 1:55 AM, Smith Joel (HEALTH AND SOCIAL CARE INFORMATION CENTRE) joel....@hscic.gov.uk wrote:

I have the clients subscribe to a group dev, uat, live etc as appropriate. You can then filter appropriately based on what the desired handler should do – ie pager handler only deals with live subscribers.

From: sensu...@googlegroups.com [mailto:se...@googlegroups.com] On Behalf Of Stuart Cracraft

Sent: 25 April 2016 19:13

To: sensu-users

Subject: sensu

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of dollars.

Thus far, I don’t see an obvious way to do the following

if a production page, send it via both the email handler and pager handler

if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json’s aren’t subdivided generally across dev, qa, uat, stage, production, and infrastructure.

I want something simple so that I don’t have to special-case configure everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don’t want to have to do things like lay out allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all individual *.json’s on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

This message may contain confidential information. If you are not the intended recipient please inform the

sender that you have received the message in error before deleting it.

Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents:

to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland

NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients

NHSmail provides an email address for your career in the NHS and can be accessed anywhere

6

I can and it would. I am confident about that.

But it won’t email those subdued

so that there is at least a non-paged record of non-prod after-hours alarms.

Those are the two conditions and

I am confident your suggestion of subdue hashes handles the first.

So I am now looking around for a way to do the second.

···

On Apr 27, 2016, at 1:46 AM, joel.smith1@hscic.gov.uk wrote:

Subdue allows exceptions which can be expressed as an array of hashes. Could you subdue as follows?:

“begin”: “00:00”,
“end”:“23:59”,
“exceptions”: ``[{“day”:“monday”, “begin”: “07:00”, “end”: “19:00”},{“day”:“tuesday”,"begin": "07:00", "end": "19:00"},{"day":```` "wednesday",“begin”: “07:00”, “end”: “19:00”},{“day”:```` “thursday”,"begin": "07:00", "end": "19:00"},{"day":```` "friday", “begin”: “07:00”, “end”: “19:00”}]``````

``

``

This would subdue all the time except for the times you want it to be active.

Cheers,

Joel

On Tuesday, 26 April 2016 14:38:11 UTC+1, Stuart Cracraft wrote:

Thanks! Can you send an example of a filter to block pages?

Apparently subdue can only subdue from one time to another. I haven’t been able to get it to say block 7pm to 7am PLUS all hours from 7pm Friday to 7am Sunday for non-prod.

On Apr 26, 2016, at 1:55 AM, Smith Joel (HEALTH AND SOCIAL CARE INFORMATION CENTRE) joel....@hscic.gov.uk wrote:

I have the clients subscribe to a group dev, uat, live etc as appropriate. You can then filter appropriately based on what the desired handler should do – ie pager handler only deals with live subscribers.

From: sensu...@googlegroups.com [mailto:se...@googlegroups.com] On Behalf Of Stuart Cracraft

Sent: 25 April 2016 19:13

To: sensu-users

Subject: sensu

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of dollars.

Thus far, I don’t see an obvious way to do the following

if a production page, send it via both the email handler and pager handler

if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json’s aren’t subdivided generally across dev, qa, uat, stage, production, and infrastructure.

I want something simple so that I don’t have to special-case configure everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don’t want to have to do things like lay out allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all individual *.json’s on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

This message may contain confidential information. If you are not the intended recipient please inform the

sender that you have received the message in error before deleting it.

Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents:

to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland

NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients

NHSmail provides an email address for your career in the NHS and can be accessed anywhere

7

I’ve coded around Sensu with an Ansible hack.

I don’t like the solution but the effect is practical and immediate for staff work/life balance as a burnout preventative measure.

Wish that came first in the Book of Sensu.

Oh well…

···

On Apr 27, 2016, at 5:39 AM, Stuart Cracraft smcracraft@me.com wrote:

I can and it would. I am confident about that.

But it won’t email those subdued

so that there is at least a non-paged record of non-prod after-hours alarms.

Those are the two conditions and

I am confident your suggestion of subdue hashes handles the first.

So I am now looking around for a way to do the second.

On Apr 27, 2016, at 1:46 AM, joel.smith1@hscic.gov.uk wrote:

Subdue allows exceptions which can be expressed as an array of hashes. Could you subdue as follows?:

“begin”: “00:00”,
“end”:“23:59”,
“exceptions”: ``[{“day”:“monday”, “begin”: “07:00”, “end”: “19:00”},{“day”:“tuesday”,"begin": "07:00", "end": "19:00"},{"day":```` "wednesday",“begin”: “07:00”, “end”: “19:00”},{“day”:```` “thursday”,"begin": "07:00", "end": "19:00"},{"day":```` "friday", “begin”: “07:00”, “end”: “19:00”}]``````

``

``

This would subdue all the time except for the times you want it to be active.

Cheers,

Joel

On Tuesday, 26 April 2016 14:38:11 UTC+1, Stuart Cracraft wrote:

Thanks! Can you send an example of a filter to block pages?

Apparently subdue can only subdue from one time to another. I haven’t been able to get it to say block 7pm to 7am PLUS all hours from 7pm Friday to 7am Sunday for non-prod.

On Apr 26, 2016, at 1:55 AM, Smith Joel (HEALTH AND SOCIAL CARE INFORMATION CENTRE) joel....@hscic.gov.uk wrote:

I have the clients subscribe to a group dev, uat, live etc as appropriate. You can then filter appropriately based on what the desired handler should do – ie pager handler only deals with live subscribers.

From: sensu...@googlegroups.com [mailto:se...@googlegroups.com] On Behalf Of Stuart Cracraft

Sent: 25 April 2016 19:13

To: sensu-users

Subject: sensu

I run Sensu Core. I want to save the expense and NOT own Sensu Enterprise.

So far, this has worked out nicely saving thousands and thousands of dollars.

Thus far, I don’t see an obvious way to do the following

if a production page, send it via both the email handler and pager handler

if a non-production page, send it via email only

The /etc/sensu/conf.d/*.json’s aren’t subdivided generally across dev, qa, uat, stage, production, and infrastructure.

I want something simple so that I don’t have to special-case configure everything and design it all into the build and deploy

and configuration management.

Have anyone who has set something up like that be willing to share?

I don’t want to have to do things like lay out allhosts:/etc/sensu/conf.d/client.json

changing that file with a restart of the sensu-client nor setup all individual *.json’s on the sensu server

modifying them.

This should be controllable from the Sensu server or its clients based on schedules relating to what kind of system hostname

it is (prod is prod, qa is qa, etc.) rather some huge, massive bandaid.

This message may contain confidential information. If you are not the intended recipient please inform the

sender that you have received the message in error before deleting it.

Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents:

to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland

NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients

NHSmail provides an email address for your career in the NHS and can be accessed anywhere