New · AI System Monitor

Your system watches itself. And tells you why.

The AI System Monitor follows your application servers, databases and portal around the clock. It warns you before your users notice, and when something is slow, the AI Data Assistant explains the cause in plain language, down to the program and the line.

Everything in one view

Every part of your application, measured every minute.

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.

Databases

Connections, long transactions, locks and who blocks whom, the busiest tables and indexes, storage areas and disk space.

Application servers

Agents, sessions and their memory, every request per endpoint and per minute, and the slowest calls with what was asked and answered.

The portal

How long pages and screens take in the browser, errors your users ran into, and how many people are working.

Logs

Errors in the database and server logs, collected and counted so a new problem stands out at once.

Diagnosis

Findings with advice: a statistic that covers too few tables, an area that is almost full, a session that keeps reading in a loop.

Actions

End a stuck application server session or disconnect a database user, straight from the dashboard. For administrators only.

Ask the AI Data Assistant

“Why is it slow?” Answered in seconds.

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.

Portal · AI Data Assistant
✦AI Data Assistant● your own calls
⟶ collect last 15 minutes · 412 requests ✓
⟶ compare same time, last 7 days ✓
⟶ running now application server · 2 requests ✓
⟶ locks 1 blocker · 3 waiting ✓
⟶ diagnosis 2 findings that slow requests ✓
Orders-GridData is 6 times slower than usual since 10:42. One request holds a lock on the table order in Orders-Save.p, line 214, and three calls are waiting for it. The rest of the system is normal. Ending that session or finishing the save will clear it.
✓ Create a ticket⇩ Download the analysisShow the details
Compared with normalEvery slow endpoint is weighed against the same period in the week before, so a busy morning is not a false alarm.
Only what slows you downRunning requests, lock waits and the findings that can make requests slow, nothing else.
A ticket in one clickThe analysis goes into the ticket as an attachment. No ticket system connected? Download the file and mail it.
Everyone can askA user sees the analysis of their own calls; administrators see the whole system.
Click through

From an alert to the line of code.

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.

AlertLong transactionopen for 12 minutes
→
TileLock waits1 blocker · 3 waiting
→
ConnectionSession 4127user, endpoint, since
→
Program · lineOrders-Save.p : 214end the session
Alerts that matter

Warned before your users call.

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.

A transaction stays open too longlong transaction
A user waits for a locklock wait
One connection reads far more than the othersreads × 4
An agent uses too much memoryagent memory
One connection takes most of the database workconnection share

Ready-made rules from day one; change the limits or add your own in the app, with a manual for every setting.

Built in, not bolted on

It measures without getting in the way.

The System Monitor runs next to your application with a small footprint and takes care of itself.

Every request countedResponse times per endpoint and per minute, kept compact, so you see trends over days.
Slow calls keptFor a slow call it keeps what was asked and answered, with passwords and tokens masked.
Memory kept in checkIdle application server sessions are ended after a while, biggest first, so agents stay lean.
Runs as a serviceThe collector runs as a Windows service that restarts itself, installed with one setup.
FAQ

Questions about the AI System Monitor

Do I need a separate monitoring tool?+

No. The System Monitor is part of RCD: the dashboard, the alerts and the analysis in the chat all come with it.

Does monitoring slow down my system?+

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.

Who can see what?+

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.

What about passwords in the kept requests?+

Passwords, tokens, keys and similar fields are masked before anything is stored.

Can it fix problems by itself?+

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.

Why RCD?

  • Explore and enjoy the new technical possibilities
  • Meet the modern security requirements
  • Be competitive again on the market
  • Become device independent
  • Reduce development costs
  • And many more advantages…

Questions? Interested?

Fill in the form below and we will contact you as soon as possible!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.