Skip to content
Start free

Observe · Database Monitoring

Nine database engines. Nothing installed on any of them.

Ceburu polls your databases remotely and read-only from a separate host. See the whole fleet, then open any instance to find the blocking chain or the query that is eating the CPU.

Start freeBook a demo
Database Monitoring / Fleet
Example
Example: the database fleet view lists ten instances across PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, MongoDB, Redis, Elasticsearch and Cassandra with status, connections, queries per second and blocking sessions. The engine filter steps through PostgreSQL, SQL Server and Redis; ledger-db on SQL Server is degraded with 5 blocked sessions.

Collection

Read-only, from the outside.

Monitoring runs from a separate host using remote, read-only queries. There is no agent to install on the database server, no extension to load and nothing to restart.

  • PostgreSQL, MySQL, MariaDB, Oracle, Microsoft SQL Server, MongoDB, Redis, Elasticsearch and Cassandra
  • Fleet view with engine filters
Database Monitoring / Collection
Example
Example: the Ceburu Collector on a separate monitoring host sends read-only queries to four database servers (PostgreSQL, SQL Server, Oracle and Redis) and the results flow back. Each database server shows a crossed-out agent slot: nothing is installed on it.

Blocking

Find the session holding everyone up.

Activity and Blocking views show who is waiting on whom, so the head of a blocking chain is the first thing you see — not the twentieth row of a lock table.

  • Overview, Activity and Blocking per instance
  • Databases and Engine views
  • Collections for MongoDB
Database Monitoring / Instance
Example
Example: the Blocking tab for the SQL Server instance ledger-db shows a blocking chain. Head blocker SPID 61, running UPDATE ledger and holding a lock for 42 seconds, blocks three sessions, which in turn block two more; their wait timers keep rising.

Queries

The expensive queries, ranked.

The Queries view ranks statements by the time they cost, so you can see which few deserve an index, a rewrite or a conversation with the team that owns them.

Database Monitoring / Instance
Example
Example: the Queries tab for the PostgreSQL instance orders-db-01 ranks statements by total time. SELECT … FROM orders WHERE customer_id = ? leads with 48,210 calls at 18.4 ms average, 14 minutes 47 seconds in total and 40% of query time, followed by an UPDATE on ledger and a SELECT on inventory.

Capabilities

Everything in Databases

The complete list, as it exists in the product today.

Engines

  • PostgreSQL, MySQL, MariaDB, Oracle, Microsoft SQL Server, MongoDB, Redis, Elasticsearch and Cassandra

Collection

  • Remote, read-only polling from a separate host — nothing installed on the database server

Views

  • Fleet view with engine filters
  • Per-instance pages: Overview, Activity, Blocking, Queries, Databases and Engine
  • Collections view for MongoDB

Works with AI Core

Database findings sit beside everything else.

Database health appears in the AI Core overview alongside every other module, and dashboards can mix database widgets with application, network and infrastructure ones on one board.

How AI Core works

From Databases

  • Instance health in the AI Core overview
  • Database widgets on shared dashboards

Get started

See every signal in one place.

Start with one site and one probe. Add modules as you go — the AI Core gets more useful with every source you connect.

Sign upBook a demoRead the docs (opens in a new tab)

Already have an account? Sign in to the portal