Operations | Monitoring | ITSM | DevOps | Cloud

In this blog article, you will discover how to setup a complete monitoring of your PostgreSQL server with Bleemeo. Agent setup and dashboards creation will be covered.

This blog article will cover how to monitor your nginx web server with Bleemeo, what is monitored and graphed by default and how to go further by configuring custom dashboards to have a global overview of your infrastructure.

This article describes how to monitor a (cluster of) redis server. Bleemeo will detects automatically the redis server (it can runs in a Docker container or directly on the host) and create automatically a service dashboard. This article will also covers creating a custom dashboard with additional metrics.

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.

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.

This article goal is to provide you guidance to start monitoring a small infrastructure, cluster monitoring and more complex topics won't be covered here. We also assume you are running instance on Amazon Web Services, Azure, Google Cloud, OVH, Scaleway... and we will not covering hardware monitoring like switch, routers, firewall...

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.

In this article we will show you how: To configure a dashboard to better understand your server and what's going on.

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.

Our mobile team has just released an updated version of our mobile application. We have completely reworked the navigation and make it available on iOS!