Skip to content
Nuca Systems

Send us a day of logs

Upload one day of logs and a system report. We run the analysis and tell you which of the three you have.

Three files decide most “mystery” slowness before anyone opens a ticket with anyone: the timings and thread logs, the connect logs for the same day, and a system report. You already have all three. Nothing is installed, nothing on the estate changes, and you get a one-page verdict you can put in front of any team.

Content Server version and patch level, if you know it.

Tell us who you are and we will reply with a secure, encrypted upload link for the three files. Nothing is attached to this email.

What feels slow, when it started, what has already been tried.

Files are used for this analysis only and deleted within 30 days of the verdict. See our privacy notice.

What to send

  1. 01

    Timings and thread logs, one working day

    The timing pairs tell us engine time against storage time for every open and save, and which operations issue the most statements. This is what separates failure mode one from failure mode two.

  2. 02

    Connect logs for the same day

    Connection and pool behaviour, statements and round trips per business operation. Multiplied by the round-trip time on the application’s actual path, this predicts the wall-clock time exactly.

  3. 03

    System report

    Mounts and storage options, JVM and memory, database and version currency, index and container statistics. This is where the configuration cause usually sits, and where the cheap fix is.

Encrypted upload. Logs are read only for this analysis and deleted within 30 days of the verdict. Strip user names first if your policy requires it; the timings work without them.