Workspaces with a **Pro** plan or higher can push a variety of service metrics (memory usage, disk capacity, etc.) to an [OpenTelemetry](https://opentelemetry.io/)-compatible observability provider, such as New Relic, Honeycomb, or Grafana.

Metrics streaming traffic does not count against your workspace's outbound bandwidth usage.

**Render does not emit metrics for the following service types:**

- [Static sites](/content/docs/static-sites/index.html)
- [Cron jobs](/content/docs/cronjobs/index.html)
- [One-off jobs](/content/docs/one-off-jobs/index.html)

## General setup

The following steps must be performed by a workspace [admin](/content/docs/team-members#member-roles/index.html):

1. From your workspace's home in the [Render Dashboard](https://dashboard.render.com/), select **Observability** in the left sidebar:

2. Under **Metrics Stream**, click **\+ Add destination**.

The following dialog appears:

3. Select your observability provider from the dropdown. The dialog updates to display fields specific to your provider.

If your provider isn't listed, select **Custom**. [Learn how to connect a custom provider.](/content/docs/metrics-streams#other-providers-custom/index.html)

4. Fill in the provider-specific fields.
   - See instructions for your provider [below](/content/docs/metrics-streams#provider-specific-config/index.html).
5. Click **Add destination**.

You're all set! Your provider will start receiving [reported metrics](/content/docs/metrics-streams-reference/index.html) from Render shortly.

## Provider-specific config

When creating a metrics stream for your workspace, you provide different information depending on your observability provider:

Select the tab for your provider below, along with instructions for other providers. Please also consult your provider's documentation for additional information.

If there’s a provider you’d like us to add, please submit a [feature request](https://feedback.render.com/).

#### Better Stack

Obtain both your **Ingesting host** and **Source token** with the following steps:

1. From your **Telemetry > Sources** page in Better Stack, click **Connect source**.
2. Add a descriptive **Name** (e.g., "Render Metrics Integration").
3. Select **Logs & Metrics**, then choose **Render** as the **Platform**.
4. Click **Connect source**.

Better Stack creates the new source and redirects you to its details page.

5. Copy your source's **Ingesting host** URL and **Source token**.

#### Datadog

To simplify metrics ingestion with Datadog, Render pushes metrics in Datadog's native format instead of using OpenTelemetry.

Specify your **Datadog site**, according to where your Datadog data is hosted.

For **API key**, generate a new organization-level API key from your [organization settings page](https://app.datadoghq.com/organization-settings/api-keys). You _cannot_ use an application key or a user-scoped API key.

#### Grafana

Obtain both your **Endpoint** and **API Token** with the following steps:

1. From your Grafana Cloud Portal (`grafana.com/orgs/[your-org-name]`), click **Details** for the Grafana stack you want to use:

2. Find the **OpenTelemetry** tile and click **Configure**.
3. Copy the value of **Endpoint for sending OTLP signals** (this is your **Endpoint**).
4. Under **Password / API Token**, click **Generate now**.
5. Add a token name (e.g., `render_metrics_integration`).
6. Click **Create Token**.
7. Copy the generated value starting with `glc_` (this is your **API Token**).

For more details, see the [Grafana documentation](https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/#manual-opentelemetry-setup-for-advanced-users).

#### Groundcover

Obtain both your Groundcover **Endpoint** and **API key** with the following steps:

1. From your Groundcover dashboard, select **Settings > Access > Ingestion Keys** in the sidebar.
2. Click **Create key**.
3. For **Key type**, select **Third Party**.

Each ingestion key should be dedicated to a single data source for better security and manageability.

4. Add a descriptive name (e.g., "Render Metrics Integration").
5. Click **Create**.
6. Copy your **Ingestion key** and provide it as your **API key** in the Render Dashboard.
7. Copy your **Managed OpenTelemetry endpoint** URL and provide it as your **Endpoint** in the Render Dashboard.

For more details, see the [Groundcover documentation](https://docs.groundcover.com/use-groundcover/remote-access-and-apis/ingestion-keys#creating-an-ingestion-key).

#### Honeycomb

For **Region**, select **US** or **EU** according to where your Honeycomb data is hosted.

For **API key**, create a new key with the following steps:

1. In your Honeycomb dashboard, hover over **Manage Data** on the bottom left and click **Send Data**:

2. Click **Manage API keys**.
3. Click **Create Ingest API Key**.

The following dialog appears:

4. Add a descriptive **Name** (e.g., "Render Metrics Integration").
5. Make sure **Can create services/datasets** is enabled.
6. Click **Create**.

#### New Relic

For **Region**, select **US** or **EU** according to where your New Relic data is hosted.

For **License key**, create a new key with the following steps:

1. From your New Relic [API keys page](https://one.newrelic.com/api-keys), click **Create a key**.

The following dialog appears:

2. For the **Key type**, select **Ingest - License**.
3. Add a descriptive **Name** (e.g., "Render Metrics Integration").
4. Click **Create Key**.

#### Pydantic Logfire

For **Endpoint**, select the **US** region.

Render currently supports only the **US** region for Logfire.

Obtain your Logfire **Write token** by doing the following:

1. From your Logfire dashboard, select your project.
2. Select **Settings > Write tokens** in the sidebar.
3. Click **New write token** and provide a name.
4. Click **Create token** and copy the token. Provide it as your **Write token** in the Render Dashboard.

For more details, see the [Logfire documentation](https://pydantic.dev/docs/logfire/manage/create-write-tokens/).

#### SigNoz

Obtain both your SigNoz **Endpoint** and **Ingestion key** with the following steps:

1. From your SigNoz Cloud dashboard, select **Settings > Workspace Settings** in the left sidebar.
2. Switch to the **Ingestion** tab:

3. Copy your **Ingestion URL** and provide it as your **Endpoint** in the Render Dashboard.

Make sure to include `https://` at the beginning, for example:
   
   ```plaintext
   https://ingest.us.signoz.cloud
   ```

4. Create a **\+ New ingestion key** or copy an existing one. Provide this value as your **Ingestion key** in the Render Dashboard.

After you save your changes, Render metrics start to appear in the **Metrics** tab of your SigNoz Cloud dashboard within a few minutes:

#### Other providers (custom)

Consult this section only if your observability provider isn't listed above.

Render can push service metrics to your OpenTelemetry-compatible endpoint, _if_ that endpoint authenticates requests via an API key provided as a bearer token in an `Authorization` header.

**If your provider's endpoint supports authentication via bearer token:**

1. Consult your provider's documentation to obtain your OpenTelemetry endpoint and API key.
2. Specify **Custom** as your provider in the metrics stream creation dialog, then provide your endpoint and API key in the corresponding fields.

**If your provider's endpoint requires a different authentication method:**

1. Please [submit a feature request](https://feedback.render.com/) to let us know about your provider's requirements.
2. You can spin up your own OpenTelemetry collector (such as the official [vendor-agnostic implementation](https://github.com/open-telemetry/opentelemetry-collector)). Your collector's endpoint can receive metrics from Render, then transform and forward them to your provider using whatever authentication method it expects.

## Supported metrics

For the full list of OTel metrics streamed by Render, see the [symbol reference](/content/docs/metrics-streams-reference/index.html).