sensu

Sensu Classic (EOL)
1

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 disagree with the premise that "this should be controllable from the
sensu server or its clients". Configuration management is exactly
where the complexity of this kind of business logic should live in my
opinion.

It is true that with filters and extra client attributes you *can* get
enough flexibility out of sensu to do some things like this, but long
term a purpose built tool like puppet or chef is the way to go to
contain this kind of complexity. Then on the sensu side the checks in
non-production don't page, because they don't even have the paging
handler in the first place, etc.

···

On Mon, Apr 25, 2016 at 11:12 AM, Stuart Cracraft <smcracraft@gmail.com> wrote:

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

That’s the standard, modern reply good for sites that have built up with CM from the start,
but it fails HORRIBLY when one has a large environment PRE-EXISTING.

That’s why the tools need to remain strong from the start.

I don’t want to start viewing CM as a way of keeping weak systems, weak apps and weak clouds functioning.

That seems anti-engineering and very band-aid.

···

On Tuesday, April 26, 2016 at 7:55:10 AM UTC-7, Kyle Anderson wrote:

I disagree with the premise that “this should be controllable from the
sensu server or its clients”. Configuration management is exactly
where the complexity of this kind of business logic should live in my
opinion.

It is true that with filters and extra client attributes you can get
enough flexibility out of sensu to do some things like this, but long
term a purpose built tool like puppet or chef is the way to go to
contain this kind of complexity. Then on the sensu side the checks in
non-production don’t page, because they don’t even have the paging
handler in the first place, etc.

On Mon, Apr 25, 2016 at 11:12 AM, Stuart Cracraft smcra...@gmail.com wrote:

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.