> 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/confluent-cloud.md).

# Confluent Cloud

Collect metrics from your Confluent Cloud Kafka clusters and connectors

groundcover supports collecting metrics from Confluent Cloud, so you can visualize your Kafka clusters' and connectors' performance and set up monitors on them.

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

## Prerequisites

You'll need a Confluent Cloud API key with access to the [Metrics API](https://docs.confluent.io/cloud/current/monitoring/metrics-api.html), and the resource IDs of the Kafka clusters (and, optionally, connectors) you want metrics for.

{% hint style="warning" %}
The Metrics API requires an API key that is **resource-scoped for resource management**, with the **MetricsViewer** role assigned to it. A Kafka-cluster-scoped API key will not work and causes an authentication error.
{% endhint %}

* **Kafka cluster resource IDs** start with `lkc-` and are found on each cluster's **Cluster settings** page.
* **Connector resource IDs** start with `lcc-` and are found on each connector's settings page.

## Adding the Confluent Cloud Integration

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

Provide the following parameters:

1. **Kafka cluster resource IDs** — one or more `lkc-...` IDs. At least one is required.
2. **Connector resource IDs** (optional) — one or more `lcc-...` IDs, if you also want connector metrics.
3. **Authentication** — your Confluent Cloud API key and secret, sent as HTTP basic auth.
4. **Scrape interval and timeout** — control the cadence of scraping.

groundcover queries Confluent's Metrics API directly (`api.telemetry.confluent.cloud`) — there's no exporter or agent to run yourself.

For the full list of metrics Confluent Cloud exposes through the Metrics API, see [Confluent's Metrics reference](https://docs.confluent.io/cloud/current/monitoring/metrics-api.html#metrics-reference).


---

# 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/confluent-cloud.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.