---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# PostgreSQL check

# PostgreSQL check {#ariaid-title1}

Release version: Brazil  
Updated September 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Credential and permission requirements for the PostgreSQL checks that monitor database size, statistics, connections, and
locks.

## PostgreSQL database account {#postgresql-check__section_gcw_d1v_skc}

The database user configured in the ServiceNow credential must meet the following requirements.

* Required for every check in this group: the account must be allowed to authenticate and connect to the specific database named in `--database`. It needs `CONNECT` privilege on that database, and `pg_hba.conf` on the server must permit login from the agent host for that user and database combination.
* Required only for `postgresql.check-connections` and `postgresql.metric-active-connections`: the `pg_monitor` role on `Postgres 10+`, or superuser. Both checks query `pg_stat_activity` across all databases and sessions.
{#postgresql-check__ul_tjq_f1v_skc}  
Configuration Prerequisites:  
The Postgres TCP endpoint must be reachable from the agent host.

* `pg_hba.conf` must let the agent host's source IP to authenticate for this user and database.
* The connection `sslmode=disable` is hard-coded. If the server enforces SSL/TLS only through `hostssl` entries, the check fails with an SSL-negotiation error that can look like an authentication failure.
* Confirm `pg_monitor` is granted if you're using connection or stats metrics.
{#postgresql-check__ul_igp_j1v_skc}