Stay organized with collections Save and categorize content based on your preferences.
This document describes how to configure your Google Kubernetes Engine deployment so that you can use Google Cloud Managed Service for Prometheus to collect metrics from RabbitMQ. This document shows you how to do the following:
These instructions apply only if you are using managed collection with Managed Service for Prometheus. If you are using self-deployed collection, then see the RabbitMQ documentation for installation information.
These instructions are provided as an example and are expected to work in most Kubernetes environments. If you are having trouble installing an application or exporter due to restrictive security or organizational policies, then we recommend you consult open-source documentation for support.
For information about RabbitMQ, see RabbitMQ.
PrerequisitesTo collect metrics from the RabbitMQ exporter by using Managed Service for Prometheus and managed collection, your deployment must meet the following requirements:
rabbitmq
version v3.8.0 or later.
For more information about available dashboards, see View dashboards.
RabbitMQ exposes Prometheus-format metrics automatically; you don't have to install it separately. To verify that the RabbitMQ exporter is emitting metrics on the expected endpoints, do the following:
kubectl -n NAMESPACE_NAME port-forward POD_NAME 15692
localhost:15692/metrics
by using the browser or the curl
utility in another terminal session.For target discovery, the Managed Service for Prometheus Operator requires a PodMonitoring resource that corresponds to the RabbitMQ exporter in the same namespace.
You can use the following PodMonitoring configuration:
Ensure that the values of the
port
and
matchLabels
fields match those of the RabbitMQ pods that you want to monitor. RabbitMQ deployed by the
operatorcontains the labels
app.kubernetes.io/component: rabbitmq
and
prometheus
port.
To apply configuration changes from a local file, run the following command:
kubectl apply -n NAMESPACE_NAME -f FILE_NAME
You can also use Terraform to manage your configurations.
Define rules and alertsYou can use the following Rules
configuration to define alerts on your RabbitMQ metrics:
To apply configuration changes from a local file, run the following command:
kubectl apply -n NAMESPACE_NAME -f FILE_NAME
You can also use Terraform to manage your configurations.
For more information about applying rules to your cluster, see Managed rule evaluation and alerting.
You can adjust the alert thresholds to suit your application.
Verify the configurationYou can use Metrics Explorer to verify that you correctly configured the RabbitMQ exporter. It might take one or two minutes for Cloud Monitoring to ingest your metrics.
To verify the metrics are ingested, do the following:
In the Google Cloud console, go to the leaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
up{job="rabbitmq", cluster="CLUSTER_NAME", namespace="NAMESPACE_NAME"}
The Cloud Monitoring integration includes the RabbitMQ Prometheus Overview dashboard. Dashboards are automatically installed when you configure the integration. You can also view static previews of dashboards without installing the integration.
To view an installed dashboard, do the following:
In the Google Cloud console, go to the Dashboards page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
To view a static preview of the dashboard, do the following:
In the Google Cloud console, go to the Integrations page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
For information about troubleshooting metric ingestion problems, see Problems with collection from exporters in Troubleshooting ingestion-side problems.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-11 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4