This is part 4 in a series on monitoring Kubernetes and Docker. Catch up on parts 1, 2, and 3.
Photo by Nareeta Martin on Unsplash
Articles
Not too long ago, in the Sensu Community Slack, the question: “Why Sensu instead of Nagios?” arose. Specifically, “How do I convince my boss to choose Sensu over Nagios?” I responded to the thread but decided it was worthwhile to share my response with the wider community. At Willis Towers Watson, we moved from Nagios to Sensu 1.2 almost a year ago (and now, we’re upgrading to Sensu Go). In this post, I’ll share what we learned and why we migrated (and why you should, too).
Sensu bean, that is.
This is a guest post to the Sensu Blog by Michael Eves, member to the Sensu community. He offered to share his experience as a user in his own words, which you can do too by emailing . Learn all about the community at sensuapp.org/community .
Considering Sensu
When people look for metrics collection for their environment they often look towards the same few solutions like Collectd, Telegraf, etc. This is for good reason: those options provide flexible & extensible metrics collection…and so can Sensu.
Sensu works quite well for metrics. I’d like to show you how to set it up.
