Grafana_

An Appwrite native PostgreSQL database exposes a standard managed PostgreSQL 18 or 17 engine, so Grafana connects to it through the built-in PostgreSQL data source with no Appwrite-specific configuration. Point the data source at your database hostname, authenticate with a read-only reporting role, and query your tables to build dashboards and alerts.

Create a reporting role

Dashboards should not connect as the primary admin user, which owns the database and can run schema changes. Create a PostgreSQL role for Grafana from the Roles tab of your database in the Console, then grant it the SELECT privileges your dashboards need from the SQL editor or psql.

Use that role's name and password in the Grafana data source below. For more about retrieving credentials, rotating the primary password, and managing database roles, see Connections.

Choose a connection target

Grafana holds its data source connections open for the lifetime of the process. Long-lived connections should use either the direct PostgreSQL port 5432 or a connection pooler running in session mode.

Do not point Grafana at the transaction-mode pooler. Transaction mode hands a backend connection back to the pool after every statement, which breaks the session assumptions Grafana relies on for connection reuse and prepared statements. For a typical dashboard workload the direct PostgreSQL port is the simplest choice. See the pooler modes page for the trade-offs.

Add the PostgreSQL data source

In Grafana, open Connections > Data sources > Add data source and select PostgreSQL. Fill in the connection details using the values from your native PostgreSQL database:

Regions are fra, nyc, sfo, sgp, syd, and tor. The edge proxy terminates TLS for every native PostgreSQL database, so TLS/SSL Mode require works with no certificate upload.

If you use Grafana Cloud and restrict database access with an IP allowlist, add the Grafana Cloud outbound IP ranges for your stack to the database allowlist. Grafana Cloud can reach the public Appwrite database hostname directly. Private connectivity features are only needed when the database is on a private network.

Under Connection limits, keep the connection counts modest so Grafana doesn't exhaust the engine's connection budget. Max open caps total connections from this Grafana instance, Max idle caps pooled idle connections, and Max lifetime recycles connections after the given number of seconds. Select Save & test to verify connectivity.

Provision from YAML

Instead of configuring the data source by hand, you can provision it declaratively. Drop a file into Grafana's provisioning/datasources/ directory and read the password from an environment variable so it never lands in source control:

apiVersion: 1

datasources:
  - name: Appwrite native PostgreSQL
    type: postgres
    url: db-<hash>.<region>.appwrite.center:5432
    user: grafana_ro
    jsonData:
      database: <database>
      sslmode: require
      postgresVersion: 1500
      maxOpenConns: 5
      maxIdleConns: 2
      maxIdleConnsAuto: true
      connMaxLifetime: 14400
    secureJsonData:
      password: $GRAFANA_DB_PASSWORD
    editable: false

postgresVersion takes Grafana's encoded version values (1500 for PostgreSQL 15, currently the highest option), so pick the highest value available for a native PostgreSQL database. The database key lives under jsonData in current Grafana releases, and Grafana expands $GRAFANA_DB_PASSWORD from the process environment when it loads the provisioning file. See the PostgreSQL data source docs for every available field.

Build a panel

With the data source connected, create a dashboard and add a panel backed by it. Switch the query editor to code mode and write a read-only query against your tables. For example, to plot daily sign-ups from a users table over time:

SELECT
  date_trunc('day', created_at) AS time,
  count(*) AS signups
FROM users
GROUP BY 1
ORDER BY 1

Grafana maps the time column to the panel's time axis and signups to the value. Because the data source authenticates as a read-only reporting role, any query that attempts to write fails at the database, which keeps a misconfigured panel from mutating production data.

Related