v0.8.1

Monitoring follows the object rules

A statement somebody else ran was the one place a hidden name could still appear: the monitoring panel listed every table's statistics and every slow query and active session to anyone who could open the datasource.

• The scoped provider now covers the five monitoring reads: a table's and an index's statistics by the table's address, and a slow query or an active session by the statement it carries, kept only when the same scanner the execution gate uses finds it names nothing hidden, and dropped when it cannot be read at all.
• /api/db/monitoring and the agent's operations readings go through it. An engine with no containers reports an empty schema, so the address there is the name alone.

See docs/CONTEXT.md §4.56.

Image: ghcr.io/klinux/dbportal:0.8.1 · chart 0.1.33.