Global Log (diagnostic log)¶
The Global Log (menu item "Global Log", address /diagnose-log) is an instance-wide, filtered event log of Vesana's own components — for troubleshooting directly in the interface, without digging through container logs over SSH. You only see what your permission covers:
| Permission | View |
|---|---|
system_log.view_own |
only events you triggered yourself (without check results) |
system_log.view_tenant |
all events of your tenants (without instance-wide events) |
system_log.view_global |
everything, including instance-wide events |
Anyone allowed to see a host (hosts.view) sees its results, status changes, flapping and connection events even without these permissions — in host detail under History, which embeds the same view limited to the host.
What ends up here¶
| Category | Examples |
|---|---|
| Connection | Agent/collector auth errors (wrong token, IP), agent/collector offline ↔ online, rejection because of too many requests |
| Mail / notification | Delivery of a notification — success, failure and skipped by a channel filter; push subscriptions with changed device keys |
| Suppressed | Notifications that were not sent, with reason (maintenance, dependency/host unreachable, collector offline, rule disabled, no matching rule …) |
| Check change | Check created, changed, deleted; check dropped from the configuration (deleted/foreign script) |
| Status change | Every change of a check, including the drop to NO_DATA (collector/agent offline, check overdue) |
| Check result | Every incoming result (see below) |
| Flapping | Flapping detected / resolved, including a short history timeline |
| Authentication | 2FA lockouts, SSO and LDAP logins |
| Update | Updates of the instance |
| Support | Support bundles |
| DB maintenance | Database self-maintenance (retention, compression), failed scheduled backups, disabled maintenance rules |
| Result processing | Problems processing incoming results (see below) |
| AI | Provider unreachable in chat or analysis, analysis result not saved, rejected connection test |
| Certificate | Issuance, renewal and expiry of the server certificate |
| Security | Content Security Policy violations reported by browsers (at most once a day per source and page, with a counter; no IP, no addresses with parameters) |
Predefined tabs: All, Problems, Connection & agents, Alerts & mail, Check changes, Status changes, Check results, Flapping.
Notifications live here¶
There is no separate "notification log" page — notifications appear in the Alerts & mail tab. Every delivery creates an entry with channel, reason (alert/recovery/test/SSL certificate), affected host/check, recipients (for push: number of devices reached) and the error, if any. Notifications without a check ("device unreachable") are listed there too.
The "All" tab also reads check results¶
The All tab really shows everything: system events and raw check results — the latter are read from the check results at display time, not stored twice. If you want only the messages without the flood of results, use another tab or filter by category.
Making processing problems visible¶
If a single result arrives unreadable (e.g. corrupt JSON), only that one result is skipped and noted here — the whole batch is not discarded. Also reported: results that cannot be assigned to a check, results of a check that has since been deleted, and batches that end up permanently unprocessable in the dead letters.
Filtering¶
Filter by severity, category, event type, tenant, host, collector, check, status, source IP, actor, time range (relative or by calendar) and full text (message, check name, hostname, display name). Filter combinations can be saved as a tab and shared via link; a modified predefined tab can be reset to default from its menu.
Live mode¶
A Live button keeps fetching new entries (every 2 seconds) — handy while you install an agent or want to watch a configuration change.
Detail panel¶
Clicking an entry opens a side panel with full context plus a direct jump to the affected host or check. For a flapping entry the panel also shows how it came about (the last status transitions).
Related¶
- Error overview — current check problems instead of system events
- Notification channels — where notifications go
- Logs — collected device logs (a different feature from the Global Log)