Skip to main content

Monitor RabbitMQ metrics in ElasticSearch

One of the reasons we are using ElasticSearch is to bring all the metrics from multiple systems together in one place. One of the systems we want to monitor is our RabbitMQ cluster. Let's walk through the steps to get our RabbitMQ metrics send to ElasticSearch and available in Kibana.

The RabbitMQ Metrics Integration

Open up Kibana and click on the hamburger icon in the left corner. This will open up a side menu with a big ‘Add integrations’ button at the bottom.

Hit this button to go to the Integrations overview page. Here you can see the list of all available integrations.

Let’s search for “rabbitmq”. We get 2 results back.

Click on the ‘RabbitMQ Metrics’ integration to go to the installation instructions.

Install MetricBeat on Windows

The RabbitMQ metrics integration is part of MetricBeat. MetricBeat is a lightweight shipper that you can install on your servers to periodically collect metrics from the operating system and from services running on those servers (or containers).

Let’s first download MetricBeat and extract the zip file on the server(s) where your RabbitMQ cluster is running. Go to the folder where you extracted the zip and run the following command

PS C:\Windows\system32> cd "C:\Program Files\Elastic\Beats\8.2.0\MetricBeat"

PS C:\Program Files\Elastic\Beats\8.2.0\MetricBeat> .\install-service-metricbeat.ps1

The output should look like this:

Status   Name               DisplayName

------   ----               -----------

Stopped  metricbeat         metricbeat

Next step is to enable the rabbitmq module to start collecting information from our RabbitMQ cluster.

PS C:\Program Files\Elastic\Beats\8.2.0\MetricBeat> .\metricbeat.exe modules enable rabbitmq

Enabled rabbitmq

Almost there! As a last step we still need to create the necessary indices. This can be done through the following command:

PS C:\Program Files\Elastic\Beats\8.2.0\MetricBeat> .\metricbeat.exe setup

Overwriting ILM policy is disabled. Set `setup.ilm.overwrite: true` for enabling.

Index setup finished.

Loading dashboards (Kibana must be running and reachable)

Loaded dashboards

On the installation instructions page, we can check that everything is working by hitting the ‘Check data’ button.

Now we can click on the RabbitMQ Metrics Dashboard button to go to the dashboard.

Here we can find some default information about our cluster. Of course you are free to customize this dashboard to your needs.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more