Confluent Cloud
Visualize Confluent Cloud Organization, Environments, Clusters, and monitor changes through queries and alerts.
- Installation guide
- Confluent Cloud data model
Installation
Requirements
- JupiterOne requires API Key Id & API Key Secret. You need permission to create
a service account in Confluent Cloud that will be used to obtain the API Key
Id & Secret. The Service Account should have the
MetricsViewer
permission to allow the ability to pull data. - You must have permission in JupiterOne to install new integrations.
Configuration in Confluent Cloud
Create a Service Account and Grant Required Permissions
- Visit the Accounts Page.
- Toggle to the "Service Accounts" tab.
- Click the "+ Add Service Account" button.
- Enter a meaningful name and description for the service account.
- Click the "+ Add Role Assignment" button.
- Select "Organization" and choose the role "MetricsViewer".
- Click "Next" and then "Create Service Account."
Generate an API Key
- Visit the API Key Page.
- Click the "Add API Key" button.
- Select "Service Account".
- Choose the service account you created earlier with the "MetricsViewer" role and click "Next".
- Select "Cloud Resource Management" as the scope for the API key and click "Next."
- Enter a meaningful name and description for the API key and create it.
- Copy or download the API Key & API Secret. It will disappear once you close the page.
Configuration in JupiterOne
- From the top navigation of the J1 Search homepage, select Integrations
- Scroll to the Confluent Cloud integration tile and click it.
- Click the Add Configuration button and configure the following settings:
- Enter the Account Name by which you'd like to identify this Confluent
Cloud instance in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when Tag with Account Name is checked. - Enter a Description that will further assist your team when identifying the integration instance.
- Select a Polling Interval that you feel is sufficient for your monitoring
needs. You may leave this as
DISABLED
and manually execute the integration. - Enter the Confluent Cloud API Key generated for use by JupiterOne.
- Enter the Confluent Cloud API Secret generated for use by JupiterOne.
- Click Create Configuration once all values are provided.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Confluent Cloud Environment | confluent_cloud_environment | Configuration |
Confluent Cloud KSQL DB Cluster | confluent_cloud_ksql_db_cluster | Cluster |
Confluent Cloud Kafka Cluster | confluent_cloud_kafka_cluster | Cluster |
Confluent Cloud Organization | confluent_cloud_organization | Organization |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
confluent_cloud_environment | CONTAINS | confluent_cloud_kafka_cluster |
confluent_cloud_kafka_cluster | CONTAINS | confluent_cloud_ksql_db_cluster |
confluent_cloud_organization | CONTAINS | confluent_cloud_environment |