OpenTelemetry Neon DB Integration

Monitor your Neon DB project's health and performance in SigNoz by directly configuring your observability pipeline using the OpenTelemetry Protocol (OTLP). Neon supports natively exporting Postgres logs and infrastructural metrics without the need for an intermediate OpenTelemetry Collector.

Prerequisites

Before you begin, ensure you have:

A Neon project on the Scale plan. Neon offers the OpenTelemetry integration only on the Scale plan.
An instance of SigNoz Cloud

Configure the Neon Project Integration

Neon allows you to configure your OpenTelemetry endpoint directly from their web console. To start exporting metrics and logs to SigNoz Cloud:

Step 1: Add the OpenTelemetry Integration in Neon

Log into your Neon Console and go to the Integrations page.
Under the Monitor > OpenTelemetry section, click Add.
Under Telemetry to export, select Metrics, Postgres logs, or both.

*Neon DB Integration Setup - Select Data Type*

Step 2: Configure Destination

Select connection protocol as gRPC (recommended) or HTTP.
Enter SigNoz Cloud ingestion endpoint in the Endpoint URL field:

https://ingest.<region>.signoz.cloud:443

Under Authentication, select API Key. Turn on Custom header name and enter signoz-ingestion-key. In the API Key field, enter <your-ingestion-key>.

Verify these values:
- <region>: Your SigNoz Cloud region
- <your-ingestion-key>: Your SigNoz ingestion key

If you are using self-hosted SigNoz, update the endpoint to your self-hosted URL and port. An ingestion key is not required — since Neon requires an authentication method, keep API Key selected and enter any placeholder value (e.g., not-needed). The self-hosted collector does not validate this header. See Cloud → Self-Hosted for details.

Optionally, under Resource attributes, set a service.name value such as your project name. Neon applies this value to Postgres logs only. On metrics, Neon sets service.name itself: sql-metrics for Postgres, compute-pgbouncer-metrics for the connection pooler, and compute-host-metrics for compute CPU and memory. To filter metrics by project or compute, use the project_id and endpoint_id attributes.

*Neon DB Integration Setup - Destination*

Step 3: Save and Complete the Integration

Click Save to complete the setup. If successful, the integration will be listed under the Integrations page in Neon, and you will start seeing metrics and logs in SigNoz within a few minutes.

Validate

Verify the metrics are being collected by SigNoz. Neon data should start appearing in SigNoz within a few minutes.

To check for metrics, go to the Dashboards > Metrics Explorer and look for metrics prefixed with neon_ (Postgres, cache, and connection pooler) and host_ (compute CPU and memory).
Go to the Logs tab in SigNoz and query using your configured service.name to see Postgres logs.

Troubleshooting

Data is not appearing in SigNoz

Invalid Credentials: Ensure your signoz-ingestion-key is correctly populated and you have not selected "Bearer" or "Basic".
Endpoint Suffixes: Do not append /v1/metrics or /v1/logs to your endpoint URL as Neon appends this automatically. Check that your URL ends in .cloud:443 without trailing slashes.
Suspended compute: Neon sends data only while a compute is active. If scale to zero suspends the compute, no metrics or logs arrive until it starts again. To keep data flowing, turn off Scale to zero in the compute settings.

Next Steps

Import the Neon Postgres dashboard to see these metrics in ready-made panels.
Take a look at the query builder to start building dashboards with your Postgres data.
Read how to Set up Alerts in SigNoz.

Get Help

If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack. If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.