> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Navigate the Integrations Hub

> Learn how to browse, configure, and monitor integrations from the Integrations Hub in Chronosphere Observability Platform.

The *Integrations Hub* catalogs integrations that bring telemetry from third-party
sources into Chronosphere Observability Platform. Browse tiles, add configurations,
and monitor health from **Integrations** in the navigation menu.

For documentation on each integration, see
[Integrations](/ingest/xcor/integrations). In the Hub, open **Overview** or **Set up**
on an integration's detail page for in-product setup steps.

## View integrations

The catalog lists each integration as a tile with its name and a short description.
At the top of the page:

* The view toggle switches between two lists:

  * **Installed** shows integrations you have already set up.
  * **Available** shows integrations you haven't set up yet.

  A view that has no integrations is disabled.
* **Find integration** filters the current view by name, description, provider, or
  tag.

Installed tiles show a status summary: counts of instances in OK, warning, or error
states when at least one instance exists in that state.

Use pagination when a view has more tiles than fit on one page. Select a tile to
open its detail page.

## View an integration

All integrations share one catalog. On the detail page, the header shows the
integration name and a **Description** section. Tabs vary:

* Integrations with **Overview** and **Configurations** also show **Metrics** and
  **Assets** when the integration publishes a metric catalog or bundled dashboards.
* Integrations with **Set up** and **Health status** also show **Metrics** and
  **Assets** when available.
* Integrations with **Overview** and no **Configurations** tab also show **Metrics**
  and **Assets** when available.

Select the integration name in the page header to jump to another integration. The
menu lists **Installed** and **Available** sections; **Search integrations**
filters by name.

### Learn about an integration

Read **Overview** for prerequisites and collected data. Read **Set up** for
Chronosphere Collector configuration, including receivers in your Collector
configuration file.

### Review collected metrics

The **Metrics** tab lists metric name, description, unit, and type.

* Filter with **Search metric name**. For a regular expression, put the pattern
  between slashes, such as `/cpu/`.
* Select **Open in Metrics Analyzer** when the button appears to open the
  integration's metrics in the [Live Telemetry Analyzer](/investigate/analyze/telemetry-analyzer).

### View configurations and their health

When **Configurations** appears on the detail page, the tab lists each
configuration and its status. Filter by **OK**, **Warn**, **Error**, **Unknown**,
or **All**. Rows show last poll time and gateway messages when present.

When **Health status** appears alongside **Set up**, the tab charts targets your
Chronosphere Collector reaches (**OK**) versus **Missing data**.

When **Health status** appears without **Set up**, the tab charts streams labeled
**Delivering**, **Partially delivered**, and **Rejected**.

Use the time range controls on **Health status** to change the chart period.

### Use bundled assets

**Assets** lists dashboards bundled with the integration. On installed
integrations, select **Go to Dashboard** to open a dashboard.

## Configure an integration

When **New configuration** appears on the detail page, you can add configurations
in the UI or with the Chronosphere API or Chronosphere Terraform provider. Field
sets differ by integration. Otherwise, follow **Overview** or **Set up**.

### Add a configuration

1. On the integration's detail page, select **New configuration**.
2. On the **Visual editor** tab in the drawer, complete the required fields in each
   section.
3. Select **Save**.

Select the **Code config** tab to review the configuration as code. The tab states
when no code view exists for the integration.

If **Edit** opens a read-only drawer, change that configuration with Chronoctl, the
API, or Terraform.

### Edit a configuration

On **Configurations**, select **Edit**, update the **Visual editor** tab, and select
**Save**.

### Manage configurations as code

Use the Chronosphere API or Terraform provider:

* Chronosphere API: Create and manage integrations with the API, including the
  [cloud](/tooling/api-info/definition/operations/CreateCloudIntegration),
  [GCP](/tooling/api-info/definition/operations/CreateGcpMetricsIntegration), and
  [Azure](/tooling/api-info/definition/operations/CreateAzureMetricsIntegration)
  integration endpoints.
* Terraform: Manage integrations with the
  [Chronosphere Terraform provider](/tooling/infrastructure/terraform), using the
  [`chronosphere_cloud_integration`](https://registry.terraform.io/providers/chronosphereio/chronosphere/latest/docs/resources/cloud_integration),
  [`chronosphere_gcp_metrics_integration`](https://registry.terraform.io/providers/chronosphereio/chronosphere/latest/docs/resources/gcp_metrics_integration),
  and [`chronosphere_azure_metrics_integration`](https://registry.terraform.io/providers/chronosphereio/chronosphere/latest/docs/resources/azure_metrics_integration)
  resources.

## Remove an integration

* When **Configurations** appears: On that tab, select **Edit**, then **Delete
  configuration**, and confirm. Delete through the API or Terraform using the same
  resources as in [Manage configurations as code](#manage-configurations-as-code).
* When **Set up** appears: Remove the integration from your Chronosphere Collector
  configuration.
* When the detail page has **Overview** but no **Configurations** tab: Stop sending
  data using the steps on **Overview**.


## Related topics

- [Integrate with Observability Platform](/integrate.md)
- [Server integrations](/ingest/xcor/integrations/server.md)
- [Azure Event Hubs destination plugin](/ingest/pipeline/plugins/destination-plugins/azure-eventhub.md)
- [Azure Event Hubs source plugin](/ingest/pipeline/plugins/source-plugins/azure-eventhub.md)
- [Send GitHub events to Observability Platform](/ingest/third-party/github.md)