Sensu & Grafana

Sensu Go features a high degree of flexibility and is designed to monitor everything from the server rack to the
Cloud
monitor. Durch eine unbegrenzte Anzahl an Event-Pipelines, bestehend aus Filtern, Mutatoren und Handlern, können Monitoring-Ereignisse validiert und korreliert, Datenformate verändert, Benachrichtigungen gesendet, Vorfälle verwaltet und Metriken gesammelt werden.

The architecture of Sensu Go, which follows the basic idea of microservices, facilitates the integration of the monitoring system into already existing solutions and processes.

We help you with the introduction.

About

Maximum flexibility with Sensu Go

Sensu Go features a high degree of flexibility and is designed to monitor everything from the server rack to the
Cloud
monitor. Durch eine unbegrenzte Anzahl an Event-Pipelines, bestehend aus Filtern, Mutatoren und Handlern, können Monitoring-Ereignisse validiert und korreliert, Datenformate verändert, Benachrichtigungen gesendet, Vorfälle verwaltet und Metriken gesammelt werden.

The architecture of Sensu Go, which follows the basic idea of microservices, facilitates the integration of the monitoring system into already existing solutions and processes.

We help you with the introduction.

Sensu agents, on the other hand, automatically log on to the Sensu backend or Sensu backend cluster, perform their designated checks, and continuously send keepalive messages. The publish-subscribe approach to triggering monitoring checks can save a lot of computing power compared to traditional monitoring solutions. The Sensu agents are assigned subscriptions, which can also be understood as tags. On the other hand, the monitoring checks (e.g. CPU, memory, disks, processes, etc.) are also categorized based on subscriptions. If a check is triggered and has for example the subscription “webserver”, all Sensu agents with the subscription “webserver” will execute this check.

Sensu Go comes into its own in cloud and cloud-like environments where there is a lot of dynamism and high turnover of hardware or software. With the help of automation tools such as Ansible, Chef, Puppet and SaltStack, the monitoring content in Sensu Go automatically adapts to the changed IT landscape in real time, without an administrator having to manually maintain it in the monitoring.

Further information about Sensu Go can be found on the manufacturers website www.sensu.io.

Sensu Go consists of the two components Sensu-Backend and Sensu-Agent. The communication is encrypted via WebSockets.

While the Sensu backend is the server component, the Sensu agent is installed on the systems to be monitored.

Etcd instances integrated 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 works using Raft (https://raft.github.io/), a “consensus algorithm”. If Sensu is to be used as a cluster with multiple instances, the data replicates automatically by adding additional Sensu backend instances.

Sensu agents, on the other hand, automatically log on to the Sensu backend or Sensu backend cluster, perform their designated checks, and continuously send keepalive messages. The publish-subscribe approach to triggering monitoring checks can save a lot of computing power compared to traditional monitoring solutions. The Sensu agents are assigned subscriptions, which can also be understood as tags. On the other hand, the monitoring checks (e.g. CPU, memory, disks, processes, etc.) are also categorized based on subscriptions. If a check is triggered and has for example the subscription “webserver”, all Sensu agents with the subscription “webserver” will execute this check.

Sensu Go comes into its own in cloud and cloud-like environments where there is a lot of dynamism and high turnover of hardware or software. With the help of automation tools such as Ansible, Chef, Puppet and SaltStack, the monitoring content in Sensu Go automatically adapts to the changed IT landscape in real time, without an administrator having to manually maintain it in the monitoring.

Further information about Sensu Go can be found on the manufacturers website www.sensu.io.

About

Sensu-Backend and Sensu-Agent

Sensu Go consists of the two components Sensu-Backend and Sensu-Agent. The communication is encrypted via WebSockets.

While the Sensu backend is the server component, the Sensu agent is installed on the systems to be monitored.

Etcd instances integrated 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 works using Raft (https://raft.github.io/), a “consensus algorithm”. If Sensu is to be used as a cluster with multiple instances, the data replicates automatically by adding additional Sensu backend instances.

Sensu agents, on the other hand, automatically log on to the Sensu backend or Sensu backend cluster, perform their designated checks, and continuously send keepalive messages. The publish-subscribe approach to triggering monitoring checks can save a lot of computing power compared to traditional monitoring solutions. The Sensu agents are assigned subscriptions, which can also be understood as tags. On the other hand, the monitoring checks (e.g. CPU, memory, disks, processes, etc.) are also categorized based on subscriptions. If a check is triggered and has for example the subscription “webserver”, all Sensu agents with the subscription “webserver” will execute this check.

Sensu Go comes into its own in cloud and cloud-like environments where there is a lot of dynamism and high turnover of hardware or software. With the help of automation tools such as Ansible, Chef, Puppet and SaltStack, the monitoring content in Sensu Go automatically adapts to the changed IT landscape in real time, without an administrator having to manually maintain it in the monitoring.

Further information about Sensu Go can be found on the manufacturers website www.sensu.io.

Grafana has established itself as the de facto standard for creating dashboards. Grafana can use various data sources as input, besides Graphite also TSDBs like Influxdb. The modern dashboard tool opens up completely different possibilities for inspecting the systems. Different measurement series can be correlated.

However, care should be taken not to take x number of measurements for a given metric from different tools for different evaluations. The metrics-first strategy of collecting metrics first and creating alerts and evaluations from them has proven to be a viable way to replace status checks for alerts and metrics for visualization as separate setups.

We help you with the introduction.

About

The modern dashboard tool Grafana

Grafana has established itself as the de facto standard for creating dashboards. Grafana can use various data sources as input, besides Graphite also TSDBs like Influxdb. The modern dashboard tool opens up completely different possibilities for inspecting the systems. Different measurement series can be correlated.

However, care should be taken not to take x number of measurements for a given metric from different tools for different evaluations. The metrics-first strategy of collecting metrics first and creating alerts and evaluations from them has proven to be a viable way to replace status checks for alerts and metrics for visualization as separate setups.

We help you with the introduction.