No separate monitoring product to buy and connect: the System Monitor is part of RCD and knows your application servers, databases and portal from the inside.
Connections, long transactions, locks and who blocks whom, the busiest tables and indexes, storage areas and disk space.
Agents, sessions and their memory, every request per endpoint and per minute, and the slowest calls with what was asked and answered.
How long pages and screens take in the browser, errors your users ran into, and how many people are working.
Errors in the database and server logs, collected and counted so a new problem stands out at once.
Findings with advice: a statistic that covers too few tables, an area that is almost full, a session that keeps reading in a loop.
End a stuck application server session or disconnect a database user, straight from the dashboard. For administrators only.
When the portal feels slow, just ask in the chat. The assistant gathers the measurements of the last minutes, compares them with a normal week and tells you the cause, with a ticket ready if you want one.
Every tile opens its details. In a few clicks you go from a red number to the user, the program and the line that causes it, and you can act on it.
Rules watch the measurements and send a mail when a limit is passed, once, with the details that point to the cause. Acknowledge or close an alert in the app, and the same problem does not flood your inbox.
long transactionlock waitreads × 4agent memoryconnection shareReady-made rules from day one; change the limits or add your own in the app, with a manual for every setting.
Orders-Save.p line 214The System Monitor runs next to your application with a small footprint and takes care of itself.
No. The System Monitor is part of RCD: the dashboard, the alerts and the analysis in the chat all come with it.
The measurements are taken every few minutes and request times are added up per minute, so the extra load is small. Detailed data is only kept for calls that are slow.
The dashboard and its actions are for administrators. In the chat every user can ask why it is slow, and sees the analysis of their own calls.
Passwords, tokens, keys and similar fields are masked before anything is stored.
It ends idle application server sessions to keep memory low. Everything else, like ending a busy session or disconnecting a user, is done by an administrator with one click.
Fill in the form below and we will contact you as soon as possible!
"*" indicates required fields