Watching the whole installation

Admin 4 · 3:10

An admin sees what's wrong across the whole installation, including Weik.io'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

A table of problems from weikio problems, errors first
Needs attention and the production card 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

0:01You need to see what needs attention, whether the hub is well,
0:05and who changed what, without changing anything.
0:12This is your Weik.io installation as the earlier admin videos left it. hello runs in devtest and production,
0:20with agent dev online on the hub's host and agent fi-01 at the site.
0:29weikio problems lists everything that needs attention,
0:33one row per problem, errors first.
0:36The first row is hello in devtest,
0:39where every message has failed since a newer version arrived.
0:43The second is fi-01, offline because it stopped reaching the hub.
0:48The third is hello in production, waiting with no online agent.
0:53Every detail ends with a command for more.
0:58You get the same items from the admin UI's Home page under Needs attention.
1:04Its production card says no agent is online.
1:07The list covers integrations and APIs, so fi-01 has no row here,
1:13only in the problems table.
1:18The Health page under Settings gives a state for every part of the platform.
1:22One part is offline, fi-01, the agent the problems table named.
1:28Under the parts are the hub's own log lines.
1:34The hub writes a platform log line each time it raises a problem.
1:38These three lines are the three problems the table listed.
1:42Logs under Observability cover what you run, not the hub.
1:49The block adds these lines to the drawing.
1:52weikio platform logs backend reads those lines,
1:57warnings and errors from the last fifteen minutes.
2:04Every change to the installation leaves a record in the audit log.
2:07Filter to deployments to reach Anna's row, which carries the reason she gave.
2:14The request page ties that change's records and log lines to one correlation id.
2:21The record names Anna's key as the actor and links to the deployment it changed.
2:31weikio audit query reads the trail of the last hour.
2:35The audit block is that trail, reads of it included.
2:42The marks are the table's problems: hello failing in devtest,
2:47fi-01 offline, and hello waiting.
2:50The hub wrote these lines as it raised the problems,
2:53readable from the Health page or the CLI.
2:56The audit log holds who changed what, down to Anna's key.

Next in this track

Admin 5 · 3:28 Backups, restore and upgrades