I’m working on retooling our Sensu infrastructure and would like to know what are the best practices for file, config and directory layout?
Is it normally better to lump the handlers.json into one large json file?
I’ve seen people creating a notifications.json where all the configs for anything that will send a notification is, but I haven’t seen any documentation on using that file.
How should the directory structure be setup?
Basically I’m looking for best practices.
I like how the puppet module handles this for me and makes folders for
each thing in conf.d, and a json for each instance of that thing:
./mutators
./plugins
./conf.d
./conf.d/client.json
./conf.d/filters
./conf.d/redis.json
./conf.d/extensions
./conf.d/handlers
./conf.d/handlers/default.json
./conf.d/checks
./conf.d/checks/.......
./conf.d/api.json
./conf.d/rabbitmq.json
./extensions
./extensions/handlers
./handlers
Its kinda like go fmt or a linter where I no longer have to worry
about having an opinion on such a thing because it is handled by a
computer 
(json is for computers)
On Wed, Jun 10, 2015 at 8:48 AM, Adam Stracener <adamstracener@gmail.com> wrote:
I'm working on retooling our Sensu infrastructure and would like to know
what are the best practices for file, config and directory layout?Is it normally better to lump the handlers.json into one large json file?
I've seen people creating a notifications.json where all the configs for
anything that will send a notification is, but I haven't seen any
documentation on using that file.How should the directory structure be setup?
Basically I'm looking for best practices.