Installation Guide Summary
Congratulations - you have successfully installed and configured the Sensu services, one or more Sensu clients, and a Sensu dashboard! With this basic implementation in place, you have the core Sensu platform available for development, testing and evaluation purposes. What’s next?
The installation guide provided manual, step-by-step instructions to help the user (that’s you) learn how Sensu is installed and configured. It would not be practical to manually install Sensu on every machine you wish to monitor. It was for this reason that Sensu was designed to be deployed by a configuration management tool, such as Puppet or Chef; see the official Puppet module and Chef cookbook for more information about how to automate your Sensu deployment.
Depending on your business requirements you may be interested in learning more about how Sensu Works, or in preparing Sensu for production.
Build a Comprehensive Telemetry Solution
Conceptually, building out a monitoring solution using Sensu requires one or more Sensu servers, and automating the installation of Sensu clients on all of your machines. With this core platform in place, you’ll also need to define monitoring checks for all of the services in your application stack (e.g. proxy services, web services, database services, etc). Additionally, it may be prudent to collect and analyze metrics for the same services, by creating metric collection and metric analysis checks. Finally, no comprehensive telemetry solution would be complete without configuring notification routing groups (i.e. who gets notified for what?) and defining alerting and escalation policies via Sensu Handlers.
Deploying Sensu into Production Environments
Coming soon. If you have questions about deploying Sensu into production environments, please contact Sensu Support.
Coming soon. If you have questions about hardening Sensu, please contact Sensu Support.
Coming soon. If you have questions about scaling Sensu, please contact Sensu Support.