Sensu

Kommentare: Sensu Go is a powerful framework to build an event pipeline tailored to the needs of their users. Events can be gathered via various different ways and processed highly accurate via handlers. Sensu Go has its strength in dynamic environments and when it is interconnected with other tools of the IT environment used by administrators and managers.

Vorteile: The monitoring framework following the microservice approach gives users the ability to fully embed Sensu Go into their environment and workflows. The strengths of Sensu Go consist in giving users endless possibilities to process events using the event pipeline with filters and mutators. Handlers represent the integration to 3rd party tools, which could be everything you can think of. Every event is processed as a json object, what makes it very easy to build interfaces between Sensu Go and $product - you name it. On the other hand the agent is able to gather information in different ways. It supports several plugin output formats, what gives the possibility to choose from a pool of thousands plugins, scraping Prometheus Exporters, or just using in-house developments. Furthermore it supports to accept events/metrics via Agent API or the built-in StatsD listener. The documentation is awesome and complete. Since it is API-driven, users are able to fully automate Sensu Go using configuration management tools like Ansible, Chef, Puppet or Salt. The slack community is big and you can get help quickly.

Nachteile: Coming from classic montioring tools it takes some time to understand how Sensu Go works, but it's definitely worth it. At the moment Sensu Go brings some in-built filters (and simple filter examples in the docs) and some maintained handlers. If users want to go beyond that they need to look for community-implementations or write own filter expressions and handlers, what assumes that they are able to script or understand javascript (for filter expressions), golang or any other programming language (for handlers). What sounds like a con in one way is a pro in another, because it gives the user endless possibilities.

Kommentare: I have used sensu for 4+ years and have become a maintainer in the last couple years. I really love seeing the diverse use cases that sensu helps organizations accomplish with core features as well as the community maintained plugins. Sensu has a really great community where I have had the benefit of leveraging many community contributions but been able to give back to such an awesome community. If you ever want to get involved with `core`, `sensu-plugins`, or the various CM (config management) projects reach out to me on the community https://slack.sensu.io

Vorteile: While many monitoring solutions try to be an out of box solution that is easy to get going and perform a prescriptive path Sensu took a step back and said instead of building a product we should build a framework. By taking the stance of framework first and product second what you get is a truly great experience where things work with little to no effort to get it spun up and going you can do so much more with it than the developers ever imagined people would use it. If you are willing to write code you can do pretty much anything you want by leveraging their framework and event pipeline. This can include writing new checks, metric gathering scripts, TSDB shippers, automated triage, automated remediation, etc.

Nachteile: Losing a lot of flexibility with filters in the transition from `sensu-ruby` to `sensu-go` but for most use cases you probably won't notice.