> For the complete documentation index, see [llms.txt](https://docs.cobrowse.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cobrowse.io/enterprise-self-hosting/gcp-terraform/google-cloud.md).

# GCP metrics configuration

If you are running the Cobrowse Enterprise Google Cloud terraform configuration, Google Cloud's [Workload Metrics](https://cloud.google.com/stackdriver/docs/solutions/gke/managing-metrics) offering is the easiest way to collect these metrics and make them available in Google Cloud Monitoring.

Please follow the [instructions supplied by Google](https://cloud.google.com/stackdriver/docs/solutions/gke/managing-metrics) to enable Workload Metrics for your cobrowse enterprise cluster. Once enabled, you will be instructed to deploy a `PodMonitor` resource which specifies which metrics to collect.

For convenience, we have provided 2 sample `PodMonitor` resources in your cobrowse enterprise for GCP terraform configuration:

{% hint style="info" %}
Consider adding configurations from the [Managing costs](https://cloud.google.com/stackdriver/docs/solutions/gke/managing-metrics#managing-costs) section of the Workload Metrics instructions to manage how often metrics are scraped and which metrics are collected
{% endhint %}

* **Redis Cluster:** `cobrowse-redis-cluster-podmonitor.yml`
  * Update the `metadata.namespace` property to the namespace where your redis cluster is deployed
* **Cobrowse:** `etc/metrics/cobrowse-svc-podmonitor.yml`
  * Update the `metadata.namespace` property to the namespace where your cobrowse services are deployed

Once the PodMonitor resources are applied to your cluster namespace, metrics should begin showing up in Cloud Monitoring in a few minutes.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.cobrowse.io/enterprise-self-hosting/gcp-terraform/google-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.