Database Monitoring

Connection health, replication lag, and slow queries across every engine an org has registered
Configure in Integrations
Databases

48

+6
Healthy

43

89.6%
Degraded

4

replication lag
Down

1

connect refused

Registered databases

PostgreSQL · MySQL / MariaDB · SQL Server · Oracle · Aurora · Redshift — credentials stored per organization

DatabaseEngineEnvConnectionsReplication lagStatus
payments

payments-prod.cluster-us-east-1

PostgreSQL 15prod184 / 4000.4sHealthy
identity

identity-prod.cluster-us-east-1

PostgreSQL 15prod96 / 3000.2sHealthy
orders

orders-prod.mysql.internal

MySQL 8.0prod271 / 30014.8sDegraded
catalog

catalog.mariadb.internal

MariaDB 11prod48 / 2000.9sHealthy
legacy-billing

legacy-billing.sqlserver.internal

SQL Server 2019prod0 / 150—Down
analytics

analytics.redshift.us-east-1

Redshiftprod22 / 1002mWatch
reporting

reporting.oracle.internal

Oracle 19cstage11 / 801.1sHealthy
sessions

sessions-stage.cluster-eu-west-1

Aurora PostgreSQLstage30 / 2000.3sHealthy

No matching results

View allView less

Catalog findings

Schema drift, volume drops, and redundancy — read from the catalog on every load, never stored

ObjectFindingDatabaseDetailSeverity
prod.orders ↔ stage.orders

commerce

Schema driftcommerce1 column missing from stage; 1 only in stage; 2 type changescritical
prod.daily_events

commerce

Volume dropcommerce94% below its 29-day mediancritical
prod.orders

commerce

Duplicate indexcommerce2 indexes on the same column (customer_id)warning
prod.payments

commerce

Duplicate rowscommerce120 duplicate rows across 120 distinct valueswarning
prod.audit_log

commerce

No primary keycommerceDuplicate rows cannot be rejectedinfo

No matching results

View allView less

Slowest queries (24h)

QueryDatabaseCallsMean
SELECT … FROM order_items JOIN orders …orders18,4022.9s
UPDATE inventory SET qty = qty - $1 …catalog9,1171.4s
SELECT … FROM ledger_entries WHERE …payments42,8800.6s
SELECT count(*) FROM sessions WHERE …sessions61,2040.2s

How database checks run

Each database an organization registers is probed on its own schedule. Credentials are held as secret references underorg_id, never in the browser.

  • Connectivity— driver-level connect with a short timeout
  • Replication— lag measured against the primary's LSN / GTID
  • Saturation— open connections against the configured pool ceiling
  • Slow queries— sampled from the engine's own statement statistics

A failed probe raises an event into the same alert pipeline as API and ETL signals, so database incidents cluster with whatever else broke at the same moment.

LoveHeartBeat - A Product from RootVyana.

v1.24.0

Theme Customizer

Explore different styles according to your preferences

Color Scheme
RTL

Change text direction

Support Chat

Toggle support chat

Navigation Type
Vertical Navbar Appearance
Horizontal Navbar Shape
Horizontal Navbar Appearance
Purchase template
customize