Operations | Monitoring | ITSM | DevOps | Cloud

Bleemeo

How to monitor your key process with Bleemeo?

This article explains how to monitor service process on your service with Bleemeo using MySQL as an example. This feature is what we called "Key Process Monitoring" and is described by our documentation. Currently, you can monitor any service process automatically discovered by Bleemeo. All metrics are detailed in our documentation, in a few words, metrics related to memory, cpu, network and i/o used by this process are gathered by the agent.

How to use Glouton as Nagios NRPE Daemon

When using Nagios, the NRPE daemon has been the traditionnal solution to implement local checks (load, number of users, custom scripts, etc.). All other checks are performed remotely from the Nagios server. NRPE daemon has been a bit challenging as you need to keep it in sync with your Nagios server and sometimes backporting this daemon can be painful. As Glouton has been implemented in Go, when you need a Nagios NRPE daemon, you can just use the binary on any compatible system and voila.

New monitoring agent in Go: Glouton

Bleemeo announces the General Availability of the new monitoring agent written in Go. This agent is the successor of the previous agent written in Python. All good aspects have been kept: Open Source, easy to deploy, and to use, available as a package for main Linux distributions: Debian/Ubuntu, CentOS/RedHat, available for Windows and available as a container.

Monitoring Apache Web Server with Bleemeo

The Apache HTTP server commonly known as Apache was officially released in 1995. Nowadays is one of the most popular HTTP servers on the World Wide Web. Many organizations such as Facebook, Cisco, IBM, and of course Apache Software foundation itself uses it. It's an open source web server, maintained by Apache Software Foundation. Apache is a cross-platform, even if the vast majority of server instances runs on Linux but some version also run on Windows.

Deploy Kubernetes on Raspberry Pi cluster with k3s

In order to carry out a demonstration of our smart tool: the Bleemeo agent at the 8th Devoxx France conference planned for the 17th of April, Bleemeo team decided to use the Kubernetes infrastructure and specially the lightweight version of Kubernetes: k3s. We choose to run k3s on a cluster of 3 Raspberry Pi nodes composed of 1 master node and 2 slaves nodes.