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

# Neon

> Point Neon's built-in OpenTelemetry log export at a Sazabi endpoint to forward Postgres logs from your Neon project without deploying an agent.

[All Neon integration capabilities](https://docs.sazabi.com/catalogs/integrations/neon)

## About

Forward Postgres logs from your Neon database into Sazabi. Neon has a built-in OpenTelemetry log export — point it at a Sazabi endpoint and your Neon project pushes Postgres logs straight into Sazabi. There is no agent or sidecar to deploy.

> [!WARNING]
>
> Neon's OpenTelemetry integration is available only on the **Scale** plan. Both the integration itself and its Postgres logs export are currently in Beta. You need admin access on the Neon project to add the integration.

## Prerequisites

* A Neon project on the **Scale** plan. The OpenTelemetry integration is Scale-only.
* Admin access on the Neon project.
* A `service.name` value to identify this project's logs in Sazabi (for example `neon-postgres-prod`).
* Your Sazabi intake URL (shown above).

## Set up in the dashboard

**Step 1**

### Open the Neon integration

In the [Neon console](https://console.neon.tech/app/projects), choose the Neon project you want to monitor, then open the project's **Integrations** page. Add the OpenTelemetry integration for Postgres logs.

**Step 2**

### Select exported data

In **Select data to export**, enable `Postgres logs` and leave `Metrics` disabled. Neon does not expose a traces export for this export. Choose the `HTTP` protocol.

**Step 3**

### Configure authentication

Configure authentication as `Bearer`. Neon adds the `Bearer` prefix to outgoing requests automatically.

> [!WARNING]
>
> Neon requires a non-empty Bearer token value, but Sazabi authenticates using
> the public key embedded in your intake URL hostname and ignores the token
> content. Use any placeholder such as `sazabi`.

**Step 4**

### Set integration values

Paste your Sazabi intake URL (shown above) into the **OTLP endpoint URL** field. Then set these values in the Neon OpenTelemetry configuration sidebar:

| Field | Value |
| - | - |
| Connection protocol | `HTTP` |
| Data to export | Postgres logs only |
| Authentication method | Bearer |
| Bearer token value | `sazabi` (any non-empty placeholder) |
| `service.name` resource attribute | `neon-postgres` (or a descriptive name for this project) |

Setting a stable `service.name` (for example `neon-postgres-prod` or `neon-checkout-db`) makes it easy to filter logs by project in Sazabi when you have more than one Neon project.

## Set up with the CLI

You can also register the Neon log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create neon --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Save the integration, then run a query against your Neon database to wake the compute if it has Scale to Zero enabled. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm Postgres log records from the **Neon** source appear within a few minutes.

If logs do not arrive after a few minutes, check the Neon integration's status panel for OTLP export errors.

## Troubleshooting

**No logs after saving the integration** — If your Neon compute has Scale to Zero enabled and is currently suspended, run a query to wake it. Suspended computes do not emit logs. Also check the integration status panel in the Neon console for OTLP export errors.

**Bearer token field rejects empty value** — Neon requires a non-empty token value. Enter any placeholder (for example `sazabi`). Sazabi authenticates via the public key in the intake URL hostname and ignores the token.

**Postgres metrics or traces are absent** — This log source exports Postgres logs only. Neon does not expose a metrics or traces export on this export.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [Instrument](https://docs.sazabi.com/guides/instrument.md)
>
> Learn how to send data to Sazabi.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.