Skip to main content
Version: 0.4 · current

Read the Overview dashboard

ConceptReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Viewer, Operator, Editor, Entity admin
PlansFree · Core · Pro · EnterpriseDeploymentSelf-hosted

The Overview answers one question for the entity chosen in the header and everything below it: is everything up, and what is at risk? This article explains each zone, how to read states, what each key figure measures and what to do when one changes.

Anatomy of the Overview​

Schematic of the Overview with eight numbered zones: view switcher, key figures, availability group card, resource cards, synthetic checks, expiry and risk, sources and the wall display button.Schematic of the Overview with eight numbered zones: view switcher, key figures, availability group card, resource cards, synthetic checks, expiry and risk, sources and the wall display button.
Figure 1. Zones of the Overview. Schematic; the numbers match the table below.
ZoneWhat it showsWhat to do
1Key figuresResources with a bar of their states, open alerts by severity, alerts you have not seen (and how many nobody acknowledged) and items expiring within 30 days. Each figure opens the list behind itStart here. A number that grew since your last look is your first lead
2Availability groupsFor each Always On availability group: listener, primary, last failover, backup preference, and every replica with its role, commit mode, health, send and redo queues, redo rate and lag. Below them, each database with its synchronization state, flagged when the replicas disagree or data movement is suspendedA replica that is not Healthy outranks any single server. Look at the databases to see which ones are behind
3Resource cardsOne card per resource, worst first: state, type, up to four tags, open alerts and the key metrics of its type, each with its value and a 60-minute sparklineSelect a card to open the resource's charts, checks and timeline
4Synthetic checksTests that exercise real paths, such as listener name resolution, linked servers, web endpoints and report rendering, with their last result and how many failA failing synthetic check means users feel it, even when every server looks healthy
5Expiry and riskCertificates and domains that expire within 30 days, soonest first; resources with nothing collected yet; and critical resources whose criticality is 4 or 5. Other expiring items, such as Key Vault secrets, count in the key figure and appear on the Checks tab of their resourceAssign an owner to each item before it becomes an outage
6SourcesEach source (the Excubius collector, New Relic, NinjaOne, Azure Monitor) with its ingest mode, whether its data is Fresh, Stale or Never seen, and when it last reportedStale data makes every other zone unreliable. Tell an administrator
7ViewsCards, Hex and Tree: three views of the same dataPick the one that fits the size of the estate (see below)
8Wall displayOpens the current view without menus, refreshing every 10 seconds, with larger type and a clockUse it on a screen in the operations room

The Overview refreshes on the rhythm you chose in personal settings, every 30 seconds by default.

States, colours and shapes​

Excubius never shows a state with colour alone: every state has its own shape and word, so the dashboard reads the same for colour-blind users, in greyscale and on a phone in sunlight.

StateShapeMeans
HealthyCircle with a tickEvery check within its thresholds
WarningTriangleAt least one check above its warning threshold
CriticalOctagonA critical threshold crossed, a check failing, or the resource unreachable
UnknownDashed circle with a question markNo check has produced a result yet
MaintenanceDashed circle, with the word MaintenanceInside a maintenance window: alerts are recorded, notifications wait
SilencedBell crossed outEvery open alert of this resource is silenced for a while

Checks that are still learning, or that only report information, count as healthy for the resource's state.

Key figures in detail​

FigureMeasuresHealthy readingWorry when
ResourcesEvery monitored resource of the entity and below, split by state. Discovered databases and linked servers follow their instance and are not counted againAlmost all greenThe red or grey part of the bar grows
Open alertsAlerts not yet resolved, by severity, security findings includedFew, and all acknowledgedA critical alert has no acknowledgement after a few minutes
Not seen by meActive alerts you have not opened yet, with how many nobody acknowledged. When your installation does not track who has seen what, this figure shows Not acknowledged insteadZero at the end of your shiftIt keeps growing: nobody is triaging
Expiring within 30 daysCertificates, domains, secrets and keys that expire soonZero, or each item has an ownerAnything under 7 days, which is critical

Three views of the same data​

  • Cards: detail per resource. Best for a team that knows its estate.
  • Hex: one hexagon per resource, coloured and shaped by state, grouped by a tag key you choose under Group by, such as env or client, or with No grouping. Best for many resources or a quick scan.
  • Tree: the entity hierarchy with resources and open alerts per branch. Select a branch to see its own Overview.

Your choice is remembered on this device, and it is part of the address (?view=hex), so a link you share opens the same view. Until you choose, the Overview opens on the view of your First screen after signing in setting.

The wall display has its own address, the Overview's with ?kiosk=1 (add &view=hex for the hex map), so a screen can open it directly. Exit wall display returns to the normal screen. Pair it with the Ops room (high contrast) theme.

note

Everything on the Overview is limited to the entities your role lets you see. Two colleagues can open the same address and see different numbers.

When nothing is monitored in the selected entity yet, the Overview says so. Entity admins see the three steps to add a first resource; everyone else is asked to contact an entity admin.

Next steps​