Sensu frequently asked questions
Thank you for visiting the Sensu FAQ! For a list of Sensu terms and definitions, see the glossary.
What platforms does Sensu support?
Is Sensu available as a hosted solution?
What are the hardware requirements for running a Sensu backed?
See the hardware requirements guide for minimum and recommended hardware to run a Sensu backend.
Is there an enterprise version of Sensu Go?
Yes! Sensu Go for enterprise is coming soon. Check out this Sensu blog post for more information about Sensu Go for enterprise.
How can I contact the Sensu sales team?
We’d love to chat about solving your organization’s monitoring challenges with Sensu. Get in touch with us using this form.
What can I monitor with Sensu?
Sensu supports a wide range of plugins for monitoring everything from the server closet to the cloud. Install the Sensu agent on the hosts you want to monitor, integrate with the Sensu API, or take advantage of proxy entities to monitor anything on your network. Check out the 200+ plugins shared by the Sensu community, including monitoring checks for AWS, Jenkins, Puppet, InfluxDB, and SNMP. You can also get started writing your own Sensu Plugins in any language using the Sensu Plugins spec.
Does Sensu include a time series database for long term storage?
Can I connect Sensu Go to clients and servers from earlier versions of Sensu Core and Sensu Enterprise?
No, Sensu Go agents and backends are not compatible with Sensu Core or Sensu Enterprise services.
Can I upgrade my Sensu version 1.x deployment to Sensu Go?
Sensu Go is a complete redesign of the original Sensu; it uses separate packages, dependencies, and data models to bring you powerful new features. (See the Sensu Go release announcement for more information.) Due to these changes, some features of Sensu 1.x are no longer supported in Sensu Go, such as standalone checks. To upgrade your Sensu 1.x deployment to Sensu Go, you’ll need to translate your Sensu 1.x configuration to the format expected by Sensu Go and install the new Sensu Go services on your infrastructure. The Sensu Go upgrading guide includes a detailed feature comparison between Sensu Go and Sensu 1.x as well as tools to help you get started.
Which ports does Sensu use?
The Sensu backend uses:
- 2379 (HTTP/HTTPS) Sensu storage client: Required for Sensu backends using an external etcd instance
- 2380 (HTTP/HTTPS) Sensu storage peer: Required for other Sensu backends in a cluster
- 3000 (HTTP/HTTPS) Sensu dashboard: Required for all Sensu backends using a Sensu dashboard
- 8080 (HTTP/HTTPS) Sensu API: Required for all users accessing the Sensu API
- 8081 (WS/WSS) Agent API: Required for all Sensu agents connecting to a Sensu backend
The Sensu agent uses:
- 3030 (TCP/UDP) Sensu agent socket: Required for Sensu agents using the agent socket
- 3031 (HTTP) Sensu agent API: Required for all users accessing the agent API
- 8125 (UDP, TCP on Windows) StatsD listener: Required for all Sensu agents using the StatsD listener
For more information, see the guide to securing Sensu.
Can one Sensu backend monitor multiple sites?
Yes, as long as the port requirements described above are met, a single Sensu backend can monitor Sensu agents at multiple sites.
Is it possible to use Uchiwa with Sensu Go?
Due to Sensu Go’s implementation, it is not possible to use Uchiwa with Sensu Go. Sensu Go does have a built-in dashboard that you can use to visually interact with your Sensu Go deployment.