---
title: Connection pooling graphs and Neon Auth enhancements
---

## New graphs for monitoring pooled connections

Neon uses PgBouncer for [connection pooling](/docs/connect/connection-pooling), allowing thousands of client connections to share a smaller pool of actual Postgres connections. The monitoring page in the Neon Console now includes **Pooler client connections** and **Pooler server connections** graphs (these display data when you use a pooled connection). The **Pooler client connections** graph shows connections from your applications to PgBouncer, while **Pooler server connections** displays the actual connections from PgBouncer to Postgres. These graphs help you understand connection usage patterns, identify bottlenecks, and determine when to adjust your pool size or compute resources. For more information, see [Monitoring dashboard](/docs/introduction/monitoring-page).

## Neon Auth now works with Vercel preview deployments

Both the [Vercel-managed](/docs/guides/vercel-managed-integration) and [Neon-managed](/docs/guides/neon-managed-vercel-integration) integrations now automatically provision Neon Auth on preview branches when enabled on your production branch. Preview deployments get the `NEON_AUTH_BASE_URL` and `VITE_NEON_AUTH_URL` environment variables configured automatically.

## GitHub Action support for Neon Auth and Data API

The [Neon Create Branch GitHub Action](https://github.com/marketplace/actions/neon-create-branch-github-action) now supports retrieving branch-specific URLs for Neon Auth and the Neon Data API. This makes it easy to run integration tests against isolated branch environments with the same auth and data access patterns you use in production. Set `get_auth_url: true` or `get_data_api_url: true` in your workflow to access the `auth_url` and `data_api_url` outputs for your test branch. Learn more about [automating branching with GitHub Actions](https://neon.com/docs/guides/branching-github-actions).

<details>
<summary>**Fixes & improvements**</summary>

- **Instagres**
  - Logical replication is now enabled by default for [Instagres](/docs/reference/instagres) databases. This lets sync engines spin up Postgres databases without needing to sign up for a Neon account to manually enable logical replication.
- **Neon CLI**
  - Fixed a misleading "org_id is required" error in the Neon CLI when running `neon branches list` without specifying a project. The CLI now provides clearer guidance when you have multiple projects, and automatically selects your project if you only have one. Upgrade your Neon CLI installation to get this fix. See [upgrade instructions](/docs/reference/cli-install#upgrade).
- **Neon Opentelemtry and Datadog integrations**
  - The [OpenTelemetry](/docs/guides/opentelemetry) and [Datadog](/docs/guides/datadog) integrations now export PgBouncer connection pooling metrics, giving you visibility into pooler client and server connections in your observability platform alongside the new charts in the Neon Console.
  - You can now edit endpoint and authentication credentials for existing [OpenTelemetry integrations](/docs/guides/opentelemetry), enabling you to fix configuration issues without having to delete and recreate the integration.
- **Monitoring**
  - Fixed monitoring graph x-axis labels to dynamically adjust based on the selected time range. When you zoom into a custom range on the graph, the labels now show more granular time information (hours instead of just day names) making it easier to read detailed metrics.
  - Fixed an issue on the monitoring page where clicking once on a chart would cause empty charts to display. Clicking on a chart now has no effect, preventing unintended empty range selections.
- **Postgres extension updates**
  - Updated the `anon` extension (PostgreSQL Anonymizer) to version 2.5.1, which fixes a table name escaping bug that could cause anonymization failures.
- **Neon Console**
  - Added a project count display to the Projects page in the Neon Console, making it easier to see how many projects you have at a glance.
  - New Neon projects created from the Neon Console are now created with a production branch only. Previously, projects created in the Neon console included both production and development branches. Projects created via the Neon CLI or API are unaffected by this changed.

</details>