Troubleshooting

The backend log

Most problems leave a trace in RDST's backend log. Open logs folder in the tray menu opens it.

The log rotates at 5 MB and keeps three older files. It can contain SQL and error messages from your database, so check it before you share it.

No notifications

1. Look at the tray menu. If it shows Notifications are blocked by Windows... Fix, click it and follow Windows notification settings.
2. Check Notifications in the tray menu is ticked.
3. Pick Send test notification in the tray menu. If the test shows up, notifications work.
4. Open Inbox, then Notification settings, and check the event is switched on under Notify me when.
5. Check Notifications a day for that database. Past the cap, alerts wait in the Inbox. A lost connection bypasses the daily cap. Its event switch and system notifications must still be on.
6. Check the alert isn't muted. Show muted in the Inbox lists muted alerts.

Notifications need RDST running. If you picked Quit RDST, nothing is watching until you open it again.

RDST can't connect

Can't reach the database in the Inbox means RDST's last checks failed.

• Click Check connection on the item to see the error and edit the host, port, user or password.
• Check the database is up and reachable from this computer, including any VPN or SSH tunnel it needs. A database inside WSL is reachable from Windows through localhost.
• After a few failures in a row RDST checks less often, up to every 15 minutes. Once a check succeeds, it starts reading again right away and closes the item.
• Database password not set means the password isn't in this computer's keychain. Enter it again in Settings.

No queries, or fewer than expected

• Waiting for queries means the database hasn't run anything since monitoring started. Point your app or a test suite at it.
• Writes are hidden. INSERT, UPDATE and DELETE statements are hidden from the list by default. Click Show writes (N) above the list.
• Filters. Check the status, table and search filters, and the time frame. Clear filters resets them.
• Only RDST's own queries. The user RDST connects as can't read other users' statistics. Grant pg_read_all_stats on PostgreSQL, or SELECT on performance_schema.* on MySQL. When RDST notices, the Inbox item's Check setup link runs the prerequisite checks again, with the fix for each.
• SQL cut off. Raise track_activity_query_size on PostgreSQL, or performance_schema_max_digest_length on MySQL, to 4096 or more.

Alerts or analyses stopped

• Sign in to resume alerts or Sign in to continue deep analysis: your Readyset sign-in expired. Recording carries on; sign in again to restart the AI checks.
• Monitoring limit reached: this database is past the database limit.
• When an automatic daily ceiling is reached, additional queries aren't queued. They're picked up the next day if they're still in the top N. You can analyze any query yourself at any time; manual runs never count toward these ceilings.
• You've run out of AI usage for now means your account's AI usage limit has been reached. Local monitoring keeps running. Use Contact us to ask for more; AI resumes once your usage is raised. See AI access.
• RDST needs about a day of readings before it alerts on changes.

RDST is slow to start after an update

An update can migrate RDST's data files on the first launch. The window says Upgrading your data, this can take a minute while it runs. Leave it to finish. If it fails, the window offers Try again and Open logs.