INC-2041 · pg-ledger-replica-2Predictive monitoring for PostgreSQL fleets
Forecast PostgreSQL saturation before it becomes an incident.
GDE collects metrics and query statistics from every PostgreSQL instance through a Go agent, forecasts where each resource is heading, and gives on-call engineers one ranked view of incidents and predictions — with SQL literals masked as positional placeholders.
- Clusters monitored
- 6
- Agents reporting
- 5 / 6
- Open incidents
- 2
- Active forecasts
- 2
Forecast crosses 340 at 13:35 UTC.
- Observed
- Forecast
- Confidence band
INC-2039 · pg-orders-primaryPRD-0187 · pg-orders-primary| Host | Cluster | Agent | Heartbeat | Status |
|---|---|---|---|---|
| db-orders-01 | pg-orders-primary | gde-agent 1.14.2 | 2s ago | Connected |
| db-ledger-03 | pg-ledger-replica-2 | gde-agent 1.14.1 | 48s ago | Stale |
| db-analytics-04 | pg-analytics | gde-agent 1.13.0 | 11:22:41 UTC | Disconnected |
Outcomes by role
One record of database risk, read three ways.
Each team gets the view it needs from the same underlying data — without exporting raw queries to get there.
Explore the Architecture →01 · Platform & SRE
See saturation coming in hours or days, not at the page.
Forecasts with confidence bands for connections, storage, and transaction ID age. Incidents and predictions live in one ranked list.
- predictive monitoring
- incident timeline
- query statistics
02 · Security & compliance
Monitoring that does not widen your data exposure.
SQL literals become positional placeholders. Tenant data is isolated, access is role-governed, agents authenticate, and privileged actions are audited.
- tenant isolation
- RBAC
- audit logging
- SQL masking
03 · Engineering leadership
Turn database risk into scheduled work.
Predictions arrive before thresholds are crossed, so capacity changes can be planned. Automated preemption remains an explicit opt-in.
- opt in preemption
- PostgreSQL
- ClickHouse
- Redis
Predictive monitoring
Forecasts with confidence bands, not single-line guesses.
GDE projects tracked metrics forward from observed history and shows the expected range. A widening band reads as uncertainty, not false precision.
Metric
- Current
- 82.6%
- At horizon
- 93.2%
- Band at horizon
- 89.3–97.1%
- Threshold
- 90.0%
- Observed
- Forecast
- Confidence band
- Threshold
Incidents & query evidence
Every incident carries its evidence.
Signals, state changes, acknowledgments, and audit records share one timeline. Query samples arrive normalized, with every literal replaced by a positional placeholder.
pg-ledger-replica-2replay_lag 12.4s exceeds warning threshold
replay_lag 48.2s — incident opened, severity Critical
Acknowledged by m.okafor · role db-oncall
incident.acknowledge · actor m.okafor
SELECT o.id, o.status FROM orders o WHERE o.customer_id = $1 AND o.created_at > $2 ORDER BY o.created_at DESC LIMIT $3
Safe opt-in preemption
Preemption stays off until you turn it on.
When a runaway session threatens a cluster, GDE can preempt it — but only under a policy an authorized role explicitly enabled.
- 01Disabled by default on every policy.
- 02Changing a policy requires the right role.
- 03Each change produces an audit record.
Policy · sample
long-running-analytics- scope
- pg-events-primary
- applies to
- role analytics_ro
- condition
- query runtime > 15 min
- changed by
- a.chen · policy-admin
Audit log
- policy.preemption.update · actor a.chen · enabled=false
Architecture
Built on components your platform team already understands.
A Go agent on your hosts, an idempotent ingestion path, and a Rails control plane backed by PostgreSQL, ClickHouse, and Redis.
Data path
GoAgentRuns beside each PostgreSQL instance and authenticates before any payload is accepted.
IngestionIdempotent writesA retried batch is recorded once — network retries never double-count.
RedisQueue & cacheBuffers work between ingestion and processing.
ClickHouseTelemetry storeTime-series metrics and normalized query statistics.
Control plane
RailsApplication & APIDashboards, incidents, forecasts, RBAC enforcement, and audit logging.
- →
PostgreSQLSystem of recordTenants, users, roles, policies, applications, and audit entries.
Security & reliability
Controls you can inspect in the product.
These are product capabilities, described as they behave. Ask us to walk through any of them against your own review checklist.
- ✓Tenant isolation
- Each tenant’s metrics, queries, incidents, and audit records are isolated.
- ✓Role-based access control
- Roles determine who can view clusters, acknowledge incidents, and change policies.
- ✓Audit logging
- Acknowledgments, role grants, policy changes, and rejected credentials are recorded.
- ✓SQL data masking
- Query literals are replaced with positional placeholders such as $1, $2, and $3.
- ✓Secure agent authentication
- Agents authenticate before GDE accepts data. Revoked credentials are rejected.
- ✓Idempotent ingestion
- Retried submissions are recorded once, so network failures never duplicate data.
- ✓Safe opt-in preemption
- Automated session preemption is off unless an authorized role enables it.
Next step
Start with one cluster.
Pick the conversation that fits where you are. Both start with the clusters you choose.