Documentation PI Nexus+ Documentation

PI Nexus+ / User Guide

Dashboard

This chapter shows how to find where the estate is unhealthy and decide what to work on first. The Dashboard has two modes: Overview for the health picture and Action View for the work queue. Your last choice is remembered in the browser.

Overview

This chapter shows how to find where the estate is unhealthy and decide what to work on first. The Dashboard has two modes: Overview for the health picture and Action View for the work queue. Your last choice is remembered in the browser.

Find the worst site and server

Overview reads from the top down: site, then type, then server, then AF database or PointSource.

Dashboard Overview with site tiles, Health by type, server cards, a service tag and an AF database row
  1. Click the site tile with the lowest health. This also chooses the site for the whole app, like the Site list.
  2. Under Health by type, click the weakest type, for example AF Analyses. Only the servers holding that type stay, and their percentage becomes that type's.
  3. Read the server cards. They are sorted worst first.
  4. Hover an amber tag, such as Unreachable or Scan overdue, for the reason. A tag is about service health, not content (see Check whether a server is reachable).
  5. Click an AF database or PointSource row to open its dialog. Rows are sorted by how many unhealthy objects they hold, so the main cause comes first.

Click the type again or choose Clear filter to see all servers. Servers PI Nexus+ does not keep current are listed under the cards as Not monitored, with the reason.

With only one site, a single Overall health tile replaces the site tiles. With nine or more sites, the seven worst are shown, plus View all sites.

See how health moved

Each site tile shows how its health changed:

  • The change since the last recorded day, for example ▲ 0.8 since yesterday (improved) or ▼ 10.2 since yesterday (dropped).
  • A line of the last 30 days. Hover it to read the first and last value.

PI Nexus+ keeps one health value per day, so a new installation shows no change and no line until a day has been recorded.

Estimated archive impact appears below the servers once compression tuning recommendations have been applied (see Compression Tuning). It is an estimate of future savings, not a measurement.

Triage the Action View

Action View puts the current work in order of impact.

Action View with the severity counts, the Monitoring sensors line, Active Issue Age, Top Errors, View all and Problem Templates
  1. Read Errors and Warnings. Click one to open the Issues page filtered to that severity.
  2. Check the Monitoring sensors line for hosts that are down; Open board opens Monitoring (see Host Monitoring).
  3. Read Active Issue Age: is the backlog new or growing old? Click a bar or segment to open those issues.
  4. Click a group under Top Errors or Top Warnings to open every issue of that type.
  5. Choose View all for the full, filterable list.
  6. Click a card under Problem Templates to open an AF Element Template whose issues reach many derived elements.

Further down, panels list the worst PI Interfaces, PI Adapters and Point Sources, and the newest issues. The Action View follows the chosen site; the panels that always cover the whole estate say so (Dashboard Reference).

A large old Error segment in Active Issue Age usually deserves attention before a larger, newer Warning segment. The Action View shows only the top groups; continue on the Issues page for the complete list.

Reference: Dashboard Reference