Skip to content

Dashboard

/dashboard is the start page after login and the only page with dashboards. It always shows exactly one dashboard: the built-in overview or one of your own or shared dashboards. There is no separate list page — you switch via the heading.

Which dashboard opens

  1. the one you viewed last,
  2. otherwise a start page set earlier,
  3. otherwise the overview.

The address then reads /dashboard/<id> or /dashboard/overview — a bookmark opens exactly that dashboard. Old links to /custom-dashboards/<id> (including variables and time range in the address) land on the same dashboard; /custom-dashboards opens the list of all dashboards.

If a dashboard does not exist (deleted, share removed, wrong link), the page says so and offers the way to the overview.

Switching

Clicking the heading opens the list:

  • search across names and owners,
  • sections Mine and Shared with me (hidden dashboards only appear under "Show all"),
  • a ⋯ per row with all actions (see below),
  • + New dashboard — enter a name, Enter creates it and opens it for editing,
  • Show all … — the management of all dashboards.
Key Effect
↑ / ↓ move through the list (wraps around)
Home / End first / last entry (when the search field is empty)
Enter open
Ctrl/Cmd + Enter, middle click open in a new tab
Menu key, Shift + F10 actions of the highlighted entry
Esc close

All dashboards

"Show all …" lists every dashboard you can see, including hidden ones:

  • clicking a row opens the dashboard; Rename (via ⋯) edits the name directly in the row (Enter or leaving the field saves, Esc reverts),
  • order by dragging the handle or with Space + arrow keys — it applies to your switcher and only to you; dragging is off while searching,
  • on the right of each row the ⋯ menu with the same actions.

Everything here takes effect immediately, there is no "Save".

Actions on a dashboard

The same list appears in the ⋯ menu of the heading, in every switcher row and in the management. What is not allowed stays visible but locked — with the reason in the text.

Action Who
Edit owner and people with an "Edit" share (permission dashboards.edit)
Rename owner only (permission dashboards.edit)
Duplicate anyone with dashboards.create — the copy belongs to you
Share … (people & teams, public link, embedding) owner only (permission dashboards.edit)
Open as TV view anyone who sees the dashboard (TV mode)
Versions … everyone can view, restoring needs edit rights
Hide / show every dashboard except the overview — only removes it from your switcher
Delete owner only (permission dashboards.create or dashboards.delete); the dashboard goes to the trash, its public link is removed
Reset to default only on your customized overview (permission dashboards.create or dashboards.delete)

The built-in overview

The overview is a dashboard made of the same widgets you can place in your own dashboards. It needs no setup and is visible to everyone; which data appears follows your permissions.

Element Content
State Share of OK in (OK + problems), below it a bar by status and the counters. Every number opens the matching error overview. With at least one open problem it never shows 100 %; without counted checks it shows "–". Downtimes and accepted exceptions do not count as problems, problems with an ACK ("in progress") do.
Tenants State per tenant. With only one tenant the block is omitted and the grid closes the gap.
Inventory Hosts, agents, collectors, newly found devices — every number is a link. Via the widget options you can add checks, running downtimes and active ACKs. A number you lack the read permission for does not appear; one that cannot be loaded right now shows "–" with a notice and "Retry".
Open problems Tabs Open · ACK · Accepted, 10 entries each, newest first; above them "N of M shown". Checks in info mode never appear, newly created ones ("waiting for data") not as a problem.
Status changes Changes per hour over the last 24 hours; clicking a bar opens a window with time, device, check, from → to and the message at that time, "Show all" leads into the Global Log.
Noisiest checks The five checks with the most changes in the last 7 days (configurable in the widget: 1 hour to 30 days, 1–20 entries); a click leads into the check history.
Devices Device list; devices can be pinned to the top, or only pinned ones shown.

On the phone the elements are stacked, the state first.

Customizing the overview

The pencil turns the overview into your own version — on the first save, not before. Pinned devices and tenants move into the widgets. The version applies only to you; "Reset to default" moves it to the trash and shows the built-in overview again. Sharing and public links exist only for your own version.

Editing

Pencil at the top right (view only on phones). Editing happens directly on the dashboard; a side panel opens on the right:

  • Widgets — catalogue with search and groups. A click places a widget at the next free spot, dragging drops it exactly where the preview shows it (Widget reference).
  • Dashboard — name, description, variables.
  • Clicking a widget opens its settings: data selection (tenants, folders, profiles, tags, check types, devices — also via variables), time range, frame and header, colours and whatever else the type offers. Duplicate and remove are there too.
  • Move widgets by the handle, resize at the bottom right; a widget is never drawn smaller than its minimum size.
  • Keyboard: arrow keys move the selected widget, Delete removes it, Ctrl+Z / Ctrl+Y undo and redo.
  • Save (also Ctrl/Cmd + Enter) applies and ends editing, Discard only asks if something changed.

Every colour in a widget states its criterion: a widget's info button shows its data selection, time range and what each colour stands for. If a widget's query fails, it shows the error with "Retry" instead of an empty list.

When a widget gets narrow, extra links fold into a menu (⋯) before titles are shortened; numbers and statuses are never cut, long names show the full text as a tooltip.

Leaving with unsaved changes — sidebar, switcher, quick search — asks: save, discard or keep editing.

If someone else has saved the same dashboard in the meantime, Vesana does not silently overwrite it: a notice offers Reload (discard your changes) or Overwrite anyway.

Every save creates a version; Vesana keeps the last 50 per dashboard, and any of them can be restored under Versions … (which again creates a version).

Time range

The time range only appears in the heading if at least one widget reads it (graph, number, gauge, heatmap, timeline, check history, status changes, noisiest checks). Presets from 15 minutes through 1 year to "All time", plus The last … (own duration) and From – to (fixed range). The chosen range and variables are in the address (?from=now-24h&var-host=…); a relative range and the variables are remembered per dashboard in this browser (90 days), a fixed range only in the address — on another computer or in a private window the dashboard's own time range applies.

Sharing

Share … (owner only) is the one way to share and has three tabs; if the dashboard already has a public link, the dialog opens on it:

Tab Content
People & teams add accounts and teams within your scope, each with View or Edit. Takes effect immediately.
Public link link without login, see below
Embed set the allowed websites, then iframe code for the public link

A dashboard belongs to its owner, not to a tenant. Everyone sees only data they have permissions for: someone with fewer permissions than the owner simply does not see the other devices and checks — a widget of which nothing is visible is omitted. If a person with fewer permissions saves the dashboard, the entries invisible to them are kept.

The link /public/d/<token> shows the dashboard without login — with the owner's permissions, limited to the tenants chosen when it was created (default: all the owner currently sees).

Field Meaning
Tenants at least one
Expires after 1, 7, 30, 90 days, 1 year or "No expiry"
Password optional
Fix variables the visitor cannot change the chosen values; the server enforces them, and they only narrow each widget's selection further

The link shows the whole dashboard, view only — including every building block of the overview (State, Open problems, Tenants, Inventory, Status changes, Noisiest checks, Devices). Counts and lists only include what lies in the selected tenants. In Inventory, "Newly found" (a discovery work list) is missing from the link; with fixed variables Agents, Collectors and Downtimes are missing too, because they cannot be limited to a single device or check. Only the Global Log is never public (it contains administrative events); the dialog names it beforehand ("Not included in the link: …") and the grid closes the gap.

Embedding: By default the link page cannot be shown in a frame (iframe) on any other site. In the Embed tab you enter, per public link, the websites allowed to embed it under Allow embedding on — one origin per line, exactly https://host or https://host:port (no path, no wildcard, at most 10). The dialog shows the iframe code only once at least one origin is saved. The setting applies only to this link and only to its page /public/d/<token>; every other Vesana page stays non-embeddable. Empty = nowhere. Revoking the link clears the list.

The link only ever queries the saved widgets: a visitor can only narrow a widget's selection via free variables, never widen it, and cannot query any data other than what the dashboard shows. Anyone calling the link's data endpoints from a script must send the widget ID. A deleted dashboard can no longer be reached through an old link. The link can be revoked at any time, a new link gets a new token.

Permissions

Permission Effect
dashboards.view see your own and shared dashboards (everyone sees the overview)
dashboards.create create, duplicate, customize the overview; also delete your own dashboards and reset your own overview
dashboards.edit edit (plus owner or "Edit" share), manage shares (owner)
dashboards.delete delete your own dashboards (owner), even without dashboards.create

Whoever may create their own dashboards may also delete them; dashboards.delete alone is enough too. A role that should not be able to delete therefore needs neither.

The data in the widgets follows services.view in the respective tenant.

Next