# Scraping Metrics from groundcover Backend

groundcover enables scraping of cloud hosts from groundcover backend without any additional installation. The configuration is managed directly in the SaaS app.

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

### Adding a Prometheus Configuration

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

<figure><img src="/files/A48JZvxnYq8P5pGQ8Nu3" alt=""><figcaption></figcaption></figure>

After entering a configuration name, you'll be asked to select the configuration type between Target Discovery and Static Targets.

### Targets Discovery

Targets discovery means groundcover will fetch the list of targets from an http endpoint with the standard method known as `http_sd`. Other target discovery methods are not supported at this point.

{% hint style="info" %}
Read more about `http_sd` [here](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#http_sd_config).
{% endhint %}

Users should 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 scheme and path - the scheme and path are common across all fetched targets
4. Authentication method for targets - the same authentication method and details will be applied across all fetched targets.

### Static Targets

As opposed to targets discovery, in static targets the user should provide the list of endpoints to scrape.

In such a case, the user should provide the following parameters:

1. Scheme - http/https
2. 1 or more endpoints
3. Path
4. Authentication method

### Common Parameters

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/prometheus/scrape-using-sensor-1.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.