---
title: "Render.com Platform"
description: "Configure Middleware integration with Render Platform to monitor apps, track logs, and detect issues in real-time."
section: "Integrations"
breadcrumb: "Integrations > Hosting Platforms > Render.com"
canonical: "https://docs.middleware.io/integrations/render-integration"
---
# Render.com Platform

[Render.com](https://render.com/) is a modern cloud platform for deploying web services, static sites, and more. Middleware enables seamless metrics and log collection from your Render.com services.

## Prerequisites

Before setting up the integration, ensure you have the following:

- A **Render.com workspace** on a **Professional** plan or higher.
- Your Middleware **API Key** (`MW_API_KEY`).
- Your Middleware **Target Endpoint** (`MW_TARGET`) to be used for Render.com's **metrics endpoint**.

## Forward Metrics to Middleware

Render.com supports streaming service metrics (CPU, memory, HTTP requests, storage, etc.) to any OpenTelemetry-compatible endpoint. Middleware can ingest these metrics using its OpenTelemetry endpoint.

Follow these steps to enable metrics forwarding from Render.com to Middleware:

### 1. Navigate to your workspace’s home in the Render Dashboard and select **Integrations**.

![Render.com integrations](/images/render/integrations.png)

### 2. From the left sidebar, select **Integrations > Observability**.

![Render.com observability](/images/render/observability.png)

### 3. Under **Metrics Stream**, click **+ Add destination**.

![Render.com metrics destination](/images/render/destination.png)

### 4. In the provider dropdown, select **Custom**.

![Render.com custom metrics stream](/images/render/custom.png)

### 5. Enter the following details:

- For `Endpoint`, enter your Middleware metrics endpoint (`MW_TARGET`).
- For `API Key`, enter your Middleware API key (`MW_API_KEY`).

![Render.com custom metric details](/images/render/details.png)

### 6. Click **Add destination**.

> **Note:** All metrics use the OpenTelemetry JSON format, and metric names are prefixed with `render` (e.g., `render.service.memory.usage`).
> Refer to the [Render Metrics Streams documentation](https://render.com/docs/metrics-streams#reported-metrics) for more details.

> **Warning:** Note that Render.com does not emit metrics for **Static sites**, **Cron jobs**, or **One-off jobs**.

## Forward Logs to Middleware

Render.com can stream logs to any syslog-compatible endpoint. Middleware supports syslog ingestion.

### **Configure Log Stream**

### 1. Navigate to your workspace’s home in the Render Dashboard and select **Integrations**.

![Render.com integrations](/images/render/integrations.png)

### 2. From the left sidebar, select **Integrations > Observability**.

![Render.com observability](/images/render/observability.png)

### 3. Under **Log Streams**, click **+ Set default**.

![Render.com log streams destination](/images/render/logdestination.png)

### 4. Enter the following details:

- For `Log Endpoint`, enter `syslog.middleware.io:5514`.
- For `Token`, enter your Middleware API key (`MW_API_KEY`).

![Render.com log stream details](/images/render/logdetails.png)

### 5. Click **Add Log Stream**.

> **Note:** Render forwards logs using the syslog protocol.
> Refer to the [Render Log Streams documentation](https://render.com/docs/log-streams) for more details.

## Reported Metrics

A detailed list of metrics collected through this integration is available in the [Render Metrics Streams documentation](https://render.com/docs/metrics-streams#reported-metrics).

## Troubleshooting

- Ensure your Middleware endpoints are accessible from Render.com.
- Verify your API keys are correct.

## References

- [Render.com Metrics Streams (Custom Provider)](https://render.com/docs/metrics-streams#other-providers-custom)
- [Render.com Log Streams](https://render.com/docs/log-streams)