Multi-receiver configuration with NRDOT Collector

Preview

We're still working on this feature, but we'd love for you to try it out!

This feature is currently provided as part of a preview pursuant to our pre-release policies.

You can configure the NRDOT Collector to monitor multiple PostgreSQL instances from one collector. This is useful if you have multiple PostgreSQL databases running on different hosts or ports and want to collect metrics from all of them using a single NRDOT Collector instance.

Prerequisites

NRDOT is installed and configured for your PostgreSQL instances:
- Self-hosted PostgreSQL

Add multi-receiver configuration

The following example shows how to configure the NRDOT Collector to monitor two PostgreSQL instances using a multi-receiver configuration. You can add more receivers as needed for additional PostgreSQL instances.

receivers:
  nrpostgresql/db1: &nrpostgresql-common
    endpoint: "<YOUR_DB1_HOST>:<YOUR_DB1_PORT>"
    username: "<YOUR_DB_USERNAME>"
    password: "<YOUR_DB_PASSWORD>"
    databases:
      - <YOUR_DB1_DATABASE_NAME>
    collection_interval: 10s
  nrpostgresql/db2:
    <<: *nrpostgresql-common
    endpoint: "<YOUR_DB2_HOST>:<YOUR_DB2_PORT>"
    databases:
      - <YOUR_DB2_DATABASE_NAME>

service:
  pipelines:
    metrics:
      receivers: [nrpostgresql/db1, nrpostgresql/db2]
      exporters: [otlp/newrelic]

Restart NRDOT Collector

Restarting is required, not optional — the collector loads its configuration once at startup and doesn't hot-reload. Any configuration change has no effect until you restart the process.

bash

$sudo systemctl restart nrdot-collector

Compatibility and prerequisites

Learn about supported PostgreSQL versions, required grants, and network requirements.

Metrics reference

Learn about the available metrics collected by the NRDOT Collector.

Troubleshooting guide

Learn how to troubleshoot common issues with PostgreSQL monitoring.