RDST Agent
RDST Agent watches your PostgreSQL and MySQL databases around the clock, tells you when a query starts taking more of the database's time, and explains what to do about it.
RDST Agent runs in the background and reads your database's query statistics every minute. It learns what normal looks like for each query, and when something changes in a way that matters, you hear about it.
Once you turn on monitoring, the agent:
- Records calls, latency and share of database time for up to 10,000 queries per database. Traffic beyond that still counts in the totals and the Other band. The top 1,000 queries get full detail.
- Spots changes that matter: a busy query getting slower, a new heavy query, a traffic spike, a query stuck for over a minute, connections near the limit.
- Deep-analyzes the heaviest queries in the background and tests the indexes and rewrites it suggests.
- Keeps a ranked list of Actions: the indexes to add or drop, the rewrites, the settings and the maintenance worth doing, with the SQL to run. It checks that each change took effect and measures whether it helped.
- Files what it finds in the Inbox, most urgent first, and sends a system notification for the things that need you now.
- Writes a nightly report on each database's day.
- Logs analyses and AI work in Agent activity, with the diagnostic statements and AI calls for each action.
RDST never writes to your database. The agent uses read-only diagnostics, and you apply any change yourself.
The agent runs inside the desktop app, which stays in your system tray (the menu bar on macOS) after you close its window. See Get Started.
What you need
| Requirement | Notes |
|---|---|
| A connected database | PostgreSQL 13+ or MySQL 8.0+. See Connect a database |
| Query statistics | pg_stat_statements on PostgreSQL, performance_schema on MySQL. RDST checks both when you turn monitoring on |
| A Readyset sign-in | AI monitoring needs it: change checks every few minutes, deep analysis and reports. An Anthropic key of your own covers deep analysis and reports, and doesn't replace signing in. See AI access |
Recording keeps working without AI. You still get the chart, the query list, and locally measured alerts, including lost connections and stuck queries.
When your account's AI usage limit is reached, AI monitoring stops gracefully, local monitoring keeps running, and the app asks you to contact us.
Guides
Turn on monitoring
Check that RDST has access to your query statistics. Turn on monitoring and watch the first readings arrive.
Actions
See the changes worth making on each database, best first, and the SQL to make them.
The Database page
See how busy your database is and which queries use most of its time.
The Inbox
Review changes on your databases and see what to do next.
Troubleshooting
Check why monitoring isn't working and find the logs.
Database permissions
Grant RDST Desktop the access it needs on PostgreSQL and MySQL. Add permissions for monitoring and Health Check when you use them.
Turn on monitoring
Check that RDST can see your database's query statistics, pick how deep analysis reads a query, and watch the first readings arrive.