Skip to content
Weik.ioUniversity
Try Weik.io

Watching the whole installation

Admin 4 · 3:00

An admin sees what's wrong across the whole installation, including the hub's own health and logs, and looks up who changed what and why in the audit log. The video continues from Admin 3.

Download the mp4Recorded on 2026.2

What it covers

  • One table of problems from weikio problems, the newest error first
  • Needs attention and the production line on the admin UI's Home page
  • Settings › Health, with every part of the platform and the hub's platform logs
  • The hub's own log lines with weikio platform logs backend
  • Anna's row in the audit log, and the records of her request under one correlation ID
  • The last hour of audit records with weikio audit query

Commands in this video

Terminal
$ weikio problems
$ weikio platform logs backend --level warn --since 15m
$ weikio audit query --since 1h
Transcript
  1. 0:01The drawing starts as video three left it.
  2. 0:04Three reads follow, and the middle one covers the hub's own parts.
  3. 0:12The hub is the platform's central server, with agent dev online.
  4. 0:17Project sandbox has hello as a deployment in both environments.
  5. 0:21The site runs agent fi-01.
  6. 0:27The problems command prints one table.
  7. 0:30Each row is one problem, and the newest error comes first.
  8. 0:34SUBJECT, SINCE, FIGURE and TITLE name every error row.
  9. 0:39Hello fails every message in devtest, fi-01 is offline,
  10. 0:44and production has no online agent.
  11. 0:47Each detail ends with the command that reads more.
  12. 0:53Home shows the same items.
  13. 0:56Needs attention holds hello at 0.1.1, failing.
  14. 1:01The production line says no agent is online.
  15. 1:04It lists integrations and APIs, so a stopped agent appears in the problems table,
  16. 1:11not in that list.
  17. 1:15The Health page lists every part of the platform.
  18. 1:18One of nine parts is offline. It names fi-01, the agent the problems table names.
  19. 1:26The hub's platform logs sit under the parts.
  20. 1:31The page holds the lines the backend wrote as it raised them.
  21. 1:35Logs under Observability hold what you run. The hub's lines are here.
  22. 1:44The block names the same three problems. weikio platform logs backend reads the same lines.
  23. 1:51A cleared problem writes an info line this read leaves out.
  24. 1:59The audit log keeps a record of every change.
  25. 2:02Anna's row names the change in devtest and her reason.
  26. 2:06The actor is her API key, and the row opens the request's page.
  27. 2:11The request's records share one correlation id.
  28. 2:15The record names its action and target.
  29. 2:22weikio audit query prints the last hour of records.
  30. 2:26Each read of the audit log writes a record.
  31. 2:34The three marks stand for the problems table's rows:
  32. 2:37hello in devtest, agent fi-01, and hello in production.
  33. 2:44The platform logs block holds the hub's own lines.
  34. 2:48The audit log keeps a record of every change.

Next in this track

Admin 5 · 3:31 Backups, restore and upgrades Watched