Optional PostgreSQL telemetry
Explain observed workload without reading customer rows.
Provider usage tells you what the platform measured. PostgreSQL statistics can add clues about the workload behind it. DatabaseMeter keeps those sources separate and telemetry optional.
Metadata, not row contents
Telemetry is limited to system catalogs, statistics views, relation sizes, hashed query fingerprints, and activity metadata. SQL text is excluded.
Qualified attribution
Language such as “largest observed workload contributor” reflects what statistics can support. It is not presented as exact billing allocation.
Read-only connection
A dedicated least-privilege role, TLS, encrypted credentials, and server-only access are required before this feature is enabled.
Optional by project
Each live project can use its own encrypted connection string for a dedicated monitoring role. Database statistics remain useful when pg_stat_statements is unavailable.
See the whole portfolio clearly.
Checking your secure session…