explain cache and set scrape interval back to 60 secs (#1103)

Author: MariadeAnton

site/content/docs/integrations/prometheus-v2.md

@@ -26,13 +26,13 @@ Activating this integration is simple.
 2. We directly create an endpoint for you and provide its URL and the required Bearer token.
 ![Prometheus integration step 2](/docs/images/integrations/prometheus_v2_step2.png)
 
-3. Create a new job in your Prometheus `prometheus.yml` config and set up a scraping interval. The scrape interval should be above 2 seconds. Add the URL (divided into `metrics_path`, `scheme` and `target`) and `bearer_token`.
+3. Create a new job in your Prometheus `prometheus.yml` config and set up a scraping interval. The scrape interval should be above 60 seconds. Add the URL (divided into `metrics_path`, `scheme` and `target`) and `bearer_token`.
 Here is an example
 
 ```yaml
 # prometheus.yml
 - job_name: 'checkly'
-  scrape_interval: 20s
+  scrape_interval: 60s
   metrics_path: '/accounts/993adb-8ac6-3432-9e80-cb43437bf263/v2/prometheus/metrics'
   bearer_token: 'lSAYpOoLtdAa7ajasoNNS234'
   scheme: https
@@ -43,7 +43,10 @@ Here is an example
 Now restart Prometheus and you should see metrics coming in.
 
 {{< warning >}}
-The Prometheus metrics endpoint has a rate limit of 50 requests per minute. We recommend using a scrape interval equal or above 2 seconds.
+The Prometheus metrics endpoint has a rate limit of 50 requests per minute.
+The responses from this endpoint are cached during 60 seconds.
+Any request made to this endpoint within 60 seconds of the initial request will receive the cached response. 
+We recommend using a scrape interval of 60 seconds.
 {{</ warning >}}
 
 ## Check Metrics