Skip to content
ROKKS Docs
DRAFTEnglish end user manual · web beta f7b7740e7371 · Android beta ed5d9494be9eDownload PDF

Monitoring and Logs

Overview

Section titled “Overview”

Monitoring views show whether the platform is healthy and what recently happened. Use them when users report failures, stale data, slow jobs, or missing dashboards.

How it works

Section titled “How it works”

Health checks show service readiness. Logs show operational events and errors. Job records show long-running work. Together they answer three questions: is the system reachable, did the requested work start, and where did it fail?

MOCKUPSource-derived illustration — not a captured product state
Source-derived System Monitor mockup
System Monitor illustration showing live health, mesh, and database performance areas.Source baseline: beta f7b7740e
MOCKUPSource-derived illustration — not a captured product state
Source-derived Logs and observability mockup
Logs illustration showing live, audit, sync, scheduler, and AI summary tabs.Source baseline: beta f7b7740e

Step-by-step

Section titled “Step-by-step”
  1. Start with the user-visible symptom.
  2. Check the Job Queue for related background work.
  3. Check monitoring for affected services.
  4. Review recent errors around the time of the issue.
  5. Fix the source problem or escalate with the job and error details.

Common mistakes

Section titled “Common mistakes”

Do not troubleshoot from browser symptoms alone. Many user-visible errors are downstream service, job, or scope issues.

Do not treat a healthy service as proof the workflow succeeded. A service can be healthy while a specific job failed.

Section titled “Related”