Skip to content

Real runs

Three runs on a demo server, as the console recorded them.

We caused each fault on purpose.First, the API stops answering.The team approved the fix once. An alert started this run, with no one at a terminal.Here is what Virca checked, changed and left alone.

Demo workspace, runs recorded November 2026.

Try it yourself. Get a link to a read-only demo workspace by email.

Where to find it in the console.

Open the execution log under Actions, then a run, then the Report tab. The cards below come from that tab.

Console: Actions in the sidebar, then a run in the execution log.
  1. Virca checks the alert first.

    Virca calls the API itself and gets no answer in 5 seconds. If it answers in time, Virca stops there and changes nothing.

    Console run record, Report tab: the API re-check got no answer in 5,003 ms.
  2. Evidence before any change.

    The app is still running. It has 10 connections open to the database, the pool limit set in the team's fix.

    Console run record: the app process is running, with 10 database connections open, the pool limit of 10.
  3. The one cause the team approved a restart for.

    No answer from the API and a full connection pool point to one cause. The team approved a restart for this cause only. For any other cause, Virca records what it found and changes nothing.

    Console run record: two pieces of evidence point to one cause, a full connection pool.
  4. Virca restarts the app only.

    The restart step accepts only the app, so the database keeps running.

    Console run record: Virca restarted the app.
  5. Then Virca re-checks.

    The API answers in 18 ms. The app is a new process. The database is the same one as before. If the API still had not answered, Virca would have marked the run failed.

    Console run record: the API answers in 18 ms, and the database process is unchanged.

Two more runs

Memory at 93%, and one batch job holds 1,609 MB.

The team's fix restarts only that job. Memory drops to 51%, and the app and the database keep running.

Console run record: memory at 93%, and one batch job holds 1,609 MB. After the fix, memory is at 51%, and the app and database are unchanged.

CPU at 76%, and the app is the top user.

The team's fix for this case only gathers facts. It saves them to the record, changes nothing and leaves the next step to the team.

Console run record: CPU at 76%, with the app active. Virca changed nothing, and the API answers.
See these runs in the demo workspace ↓

Demo

Explore the Virca demo workspace

Request a link to a read-only demo workspace. The link is sent to your email.

Illustration: an email carries the link to the demo workspace, valid for 24 hours.
Illustration: an email links to the demo workspace.
  • The link is sent to the email address you enter.
  • The link is valid for 24 hours.
  • One link is active per email address.

Request demo access

Having trouble? Open the form in a new tab

Your name, email address and request time are used to send the demo link and to follow up about Virca. Details are in the Privacy Policy.