Use Settings, the administration area in the web chat, to inspect a running installation. Metnos can also produce an HTML report that opens as a local file. It is a technical snapshot of the moment when it was generated, not a second version of Settings.
You can ask Metnos directly:
Show me where I can check the latest turns and service status.
The simplest route starts in the web chat: Settings > Activity > Turns for recent requests and Settings > System > Services for configured services. If you are talking to Metnos through Telegram, you must still open these pages in a browser because Telegram does not contain the administration area.
APIs, logs, and files are useful for technical diagnosis. The static report described below belongs to this second case and is not the ordinary route for chat users.
| Tool | Refresh behaviour | Access | Purpose |
|---|---|---|---|
Settings (/admin) | Reads data again whenever a page is opened or refreshed. | Requires a session with the administrator role. | Inspect and control the installation while it is running. |
Static report (runtime.observability) | Remains fixed at the moment when it was generated. | It is a local file; protection depends on the file and computer permissions. | Inspect six local sources offline. |
These are not two views of the same facility. Settings uses its own pages and data, while the static generator runs only from the command line and is not used by the HTTP server.
The Settings landing page summarises version and uptime, turns over the last 24 hours, proposals, executors, scheduler activity, Safety signatures, and users. Detail pages keep different operational questions separate:
| Route in the chat | Main information |
|---|---|
| Settings > Activity > Turns | Identifier, time, channel, actor, steps, outcome, duration, and request. |
| Settings > Activity > Scheduler | Task runs, outcome, and duration. |
| Settings > System > Services | Services in the canonical registry, status, and admitted controls. |
| Settings > System > Models | Effective redacted LLM, embedding, and VLM configuration: LLM and VLM can be edited and restored; embedding is view-only. |
| Settings > System > Devices | Paired devices, presence, and revocation. |
| Settings > System > Users | Users, roles, channels, and administrable preferences. |
runtime/ui_surfaces.py is the canonical description of visible
pages and their navigation routes. Tutor uses the same registry, so a
structural interface change also requires an updated navigation guide and a
rebuilt Tutor index.
The generator reads local sources and composes one document with embedded styles, no JavaScript, and no live connection to the server. Sections are ordered as follows: tests, Mnestoma, pairings, recent turns, Vaglio decisions, and scheduler.
Each collector handles an unavailable source separately. The page can therefore be produced when one section is empty or reports an error. This makes a partial snapshot readable; it does not make missing data evidence that the corresponding component is healthy.
The generated document currently uses Italian labels and
lang="it". It is not a localised chat surface and must not be
presented as one.
| Source | Data shown | Configured location |
|---|---|---|
| Mnestoma | Counts, active and proto edges, recent events. | Mnestoma's database, normally below PATH_WORKSPACE/.mnestoma. |
| Pairings | Channel, sender identifier, level, timestamps, pairing author, and revoked count. | DB_PAIRINGS below PATH_USER_STATE. |
| Turns | Latest fifteen turns: request, outcome, step count, and beginning of the answer. | PATH_TURNS below PATH_USER_DATA. |
| Vaglio | Latest twenty decisions: executor, score, outcome, and abbreviated reason. | PATH_USER_DATA/vaglio. |
| Scheduler | Enabled tasks, schedule, latest run, and outcome. | PATH_USER_STATE/scheduler_v2.sqlite. |
| Registered tests | Modules, enabled cases, latest status, and largest modules. | PATH_RUNTIME/testing/tests.db. |
Limits are fixed in the generator and cannot be changed from the command line: at most five turn files, three Vaglio files, and a bounded number of rows or events per section. The report helps direct a diagnosis; it is not a source for complete totals.
admin role; summaries may cover several users. It is not an individual user's personal view.--out.From the installation root, using the Metnos Python environment:
PYTHONPATH=runtime ./.venv/bin/python -m observability render PYTHONPATH=runtime ./.venv/bin/python -m observability render --out /chosen/path/dashboard.html
The default destination is
PATH_WORKSPACE/dashboard/index.html. The command reports the
written path and exits. There is no built-in periodic refresh: generation time
and content remain unchanged until the command runs again.
The file is derived output. It can be removed by deleting only the selected output path after confirming that no process uses it; removing it does not delete any operational source.
Focused tests for the static generator live in
tests/runtime/runtime/test_observability.py. They verify, among
other things, that executor names, requests, and responses cannot introduce
active markup into the file. HTTP and end-to-end tests cover administration
pages separately; this guide does not freeze a test count that would become
stale.
runtime/http_routes_admin.py — Settings data and actions;runtime/http_auth.py — authentication boundary for /admin routes;runtime/ui_surfaces.py — editorial registry of visible surfaces;runtime/observability.py — static snapshot generator;runtime/config.py — canonical installation paths.