# Redis Cloud

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

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

### Enabling Metrics Exporting in Redis Cloud

The integrations is based on Redis Cloud metrics exporting using a Prometheus endpoint - <https://redis.io/docs/latest/integrate/prometheus-with-redis-cloud/>.

To get started, you will need to set up [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) in Redis Cloud and extract the Prometheus endpoint.

You can then move forward with configuring the integration in groundcover.

### Adding Redis Cloud Integration

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

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FdammE0iIksuJ8CvGeMKn%2Fimage.png?alt=media&#x26;token=69145441-3985-4fdd-8602-51de102a702a" alt=""><figcaption></figcaption></figure>

We support 2 types of configuration:

1. Target discovery - provide an http endpoint from which groundcover will discover the list of hosts to scrape.
2. Static targets - provide 1 or more endpoints to scrape directly.

The following sub-sections elaborate on each option:

#### Targets Discovery Configuration

Provide the following parameters:

1. Discovery endpoint + authentication details if needed
2. Drop/Keep targets rules (optional) - this is a list of regexes indicating whether any filtering should be done on the fetched targets;
   1. Drop targets - drop all targets which match any of the regular expressions.
   2. Keep targets - drop all targets which don't match any of the regular expressions.\
      In case both drop targets and keep targets are provided, drop targets will filter out even if there is a match in keep targets.
3. Targets path - the path will be the same across all fetched targets
4. Basic authentication for targets - the same authentication method and details will be applied across all fetched targets.

#### Static Targets Configuration

In the case of static configuration, please provide the following parameters:

1. 1 or more endpoints - these are the addresses of your Redis Cloud instances.
2. Path
3. 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> .


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.groundcover.com/integrations/data-sources/redis-cloud.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.