Canalwise dev

idle

Containers

probed by the api every 15 s · CPU 100 % = one core · public hostnames probed by this browser
not connected

Storage

seen from the api container every 30 s · response time: a few ms is normal, seconds mean the disk is slow or locked
not connected

E-mail

sign-in codes, welcome mails, participation confirmations and tests sent by the server · counts only, no addresses · settings on Config
not connected

Participation requests

sent from the website's participation form · follow them up on Participation
not connected

Device catalogue

what the apps download to name the boat's devices, and what test boats forwarded · details on Devices
not connected

Jobs

scheduler state from each container · progress and log pushed by the job
no jobs yet

API log

Busiest routes