That’s why becon

  • becon is the world’s first Sensu partner
  • becon has profound experience in open source monitoring
  • becon offers the all-in-one package for Sensu

In practice

  • You have reached the limits imposed by Nagios
  • You need to scale up in order to monitor a very large infrastructure
  • You trust in industry standards for visualization and data storage

Sensu – Workflow Automation for Monitoring

Sensu is an open source monitoring event pipeline written in Golang. Sensu allows to monitor the health state of servers, virtual machines, containers, network devices, but also applications, services and counting.

Sensu offers high level flexibility and was build to monitor everything from the server rack to cloud entities. With a non limited amount of event pipelines consisting of filters, mutators and handlers, users can validate and correlate monitoring events, mutate check output, notify groups of people, manage incidents and collect metrics.

The architecture, which persues the principle of microservices, makes it easy to integrate Sensu in already existing environments and processes.

Sensu comes in two pieces: then Sensu-Backend und the Sensu-Agent. The communication is made encrypted via websockets.

While the Sensu-Backend represents the server component, the Sensu-Agent is installed on the systems to be monitored.

Etcd instances built into the Sensu-Backend are used to store configuration and live data. Etcd, which is also used by Kubernetes, is a distributed NoSQL key-value store and uses Raft (https://raft.github.io/), a “consensus algorithm”. If Sensu is to be used as a cluster with multiple instances, the data will automatically replicate by adding more Sensu-Backend instances.

On the other hand, the Sensu-Agent automatically register at the Sensu-Backend or Sensu-Backend-Cluster, perform the monitoring checks that are intended for them and continously send keepalive messages. The publish-subscribe approach to trigger montioring checks can save a lot of cpu time compared to traditional monitoring solutions. The Sensu-Agents are assigned to subscriptions, which also can be understood as tags. On the other hand, the monitoring checks (eg. CPU, memory, disks, processes, etc.) also are categorized by means of subscriptions. If a check request is triggered and has, for example, the subscription “webserver”, all Sensu-Agents with the subscription “webserver” perform this check.

Sensu unfolds it strengts in highly dynamic cloud and cloud-like environments where the fluctuation of hard- or software is high.

With the help of automation tools such as Ansible, Check, Puppet and SaltStack, the monitoring content of Sensu can automatically be adapted to the changes in the IT landscape in real time, without an administrator having to maintain it manually.

You can find additional information about Sensu on the developer’s website  www.sensu.io


  • Development of a monitoring strategy

  • Advice regarding the selection of the best open source monitoring solution

  • Architectural and security design for Sensu

  • Implementation and rollout of Sensu

  • Migration of Nagios, Naemon or Icinga to Sensu

  • Order development

  • Training

  • Support

  • Operational support

Recent Blogposts

Questions? We’ll contact you directly:

    Go to Top