> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/collect-data/data-sources/rabbitmq.md).

# RabbitMQ

Collect metrics from your RabbitMQ nodes

groundcover supports metrics collection from your RabbitMQ instances, to allow you to visualize your instances performance and set up monitors.

{% hint style="info" %}
Configuration is only enabled for Admins at this point
{% endhint %}

### Enabling Metrics Exporting in RabbitMQ

groundcover uses the prometheus exporter plugin of RabbitMQ to scrape the metrics. Before setting up the integration on groundcover side, you need to enable the rabbitMQ prometheus plugin on all nodes. To do so, follow this guide - <https://www.rabbitmq.com/docs/prometheus#enable-rabbitmq_prometheus>

### Adding RabbitMQ Integration

Navigate to [Data Sources](https://app.groundcover.com/settings/integrations/data-sources) and select RabbitMQ.

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FoSrg4Eoh9rILc5nyDVut%2Fimage.png?alt=media&amp;token=19e398f2-d2ef-4465-bdab-fa5b97641a7a" alt="Selecting RabbitMQ in the groundcover Data Sources screen"><figcaption></figcaption></figure>

#### Define the list of targets

Provide the following parameters of your RabbitMQ instances to scrape metrics from:

1. Scheme - http or https
2. 1 or more endpoints - these are the addresses of your RabbitMQ instances.
3. Path
4. Authentication method

#### Metrics Scraping Rules

On top of the targets configuration, you can also provide the following parameters:

1. Drop/Keep metrics (optional) - list of regexes of metrics to drop or keep.
   1. Drop metrics - drop all metrics that match any of the regular expressions.
   2. Keep metrics - drop all metrics that don't match any of the regular expressions.
2. Additional relabeling (optional) - prometheus can support a vast set of relabeling rules. Use this code block to apply any additional relabeling rules. Use the [relabeling cookbook](https://docs.victoriametrics.com/victoriametrics/relabeling/) to explore and configure the right releabeling rules for you.
3. Extra labels (optional) - a list of key-value pairs to be added to all scraped metrics from this configuration, such as env=production. Use the extra labels to easily filter metrics in dashboards or monitors.
4. Scrape interval and scrape timeout - control the cadence of scraping.

## Common Questions

### Where can I find scraped metrics?

All metrics in the platform can be found in the metrics exploration page:\
<https://app.groundcover.com/explore/data-explorer>

For the full list of metrics groundcover collects from RabbitMQ, each with its description, unit, type, and the labels you can slice by, see [RabbitMQ Metrics](/collect-data/data-sources/rabbitmq/rabbitmq-metrics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/collect-data/data-sources/rabbitmq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.