Choose where collection runs
The collector connects to your monitored PostgreSQL instance. Choose a location that can reach it without opening your database to the public internet.
Included shared managed collection
MyDBA operates a shared collector fleet on Fly.io. Machines can serve multiple organizations. Connection assignments and API authorization scope collection to the relevant organization. Your database must be reachable from the assigned collector; the dashboard lists managed egress addresses for allowlisting.
Included self-hosted collector software
Run the collector in your network, VM or Kubernetes cluster. It uses outbound HTTPS for MyDBA control-plane calls and telemetry ingest. Monitoring telemetry leaves your network for the hosted MyDBA service. Dashboard-managed connection credentials are stored by MyDBA; local YAML configuration lets you keep monitored-database credentials on the collector host. Running the complete platform yourself is a separate deployment and licensing path.
Optional dedicated managed machines
Shared managed collection and self-hosted collector software are included on Free and Pro. Dedicated managed collectors cost £50 per machine per month and do not increase your monitoring allowance. Dedicated machines are reserved for your connections and have a dedicated egress IP for allowlisting.
API authentication
Customer binaries contain no embedded MyDBA database credentials. The current default transport authenticates outbound HTTPS control-plane and ingest calls with your organization-scoped collector API key. It does not exchange that key for central PostgreSQL credentials or require direct access to the MyDBA database. Older internal direct-database transports are separate operational paths.
API-key validation is rate limited. Server-side authorization checks the key and organization scope before accepting telemetry or returning connection configuration.
What is collected
- Query statistics and normalized query text from
pg_stat_statements. - System views, schema metadata, performance metrics and EXPLAIN plans.
- In-flight query text from
pg_stat_activity. - PostgreSQL logs when log collection is configured.
This is monitoring telemetry, not a database backup or application-row export. Query text, logs, plans and schema definitions can nevertheless contain sensitive literals or identifiers. Some diagnostics inspect table or index pages or compute aggregates; grant only the permissions needed for the checks you enable.
Normal collection and opt-in setup writes
Normal collection reads diagnostic information. In Setup Assistant, choosing “Auto-install safe extensions” authorizes installation during the scan of available, missing pg_proctab, pgstattuple, pg_buffercache and pg_visibility, when the role has sufficient privileges. It is off by default. Preload, configuration and restart requirements are reported as manual steps.
Distribution
Collector binaries are versioned and distributed over HTTPS through Cloudflare R2. Container and Helm installation options are also available. Keep the collector updated and protect its API key and local configuration.