Which statement is slow
Sort by duration, count or rows returned, with the statement text.
Read databases at the protocol layer
MySQL, PostgreSQL, Oracle, Redis, MongoDB and ClickHouse statements are parsed inside the agent. No drivers, no connection string changes.
Database and callersDiting
01Slow statement
SELECT … WHERE order_id = ?02Service
checkout / orders03User session
Statements and requests, connected
Statement, plan, duration, rows returned and error code are recorded with the request. The DBA sees raw statements and timings.
- Top SQL and execution plans
- Aggregated by service, instance and statement
- Slow queries link to traces and sessions
- Instance auto-discovery
What this layer answers
Which instance
Instance, schema, table and plan together.
Who calls it
The statement belongs to a service and an endpoint, not to nothing.
What the user felt
Linked to the session and replay of that interaction.
Supported databases
| Relational | MySQL, PostgreSQL, Oracle |
|---|---|
| Cache and document | Redis, MongoDB |
| Analytical | ClickHouse |
| Access | Parsed on the wire by the agent. No database account, no plugin. |
Fits
- Existing systems where connection strings and drivers cannot change
- Teams that need SQL tied to services and users
Doesn't fit
- Environments that need internal lock-wait detail with Performance Schema disabled
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.