Subscription reports and service status

01In a nutshell #sec_00e8dd52

At the subscription level, the reports are the same as in each workspace — the workspace becomes a dimension — and the Services page only states what REVIEWIT observes from its own processes, without ever naming a job.

02The reports #sec_9f785f45

Supervision › Reports. The same reports as in each workspace, read at the subscription level: each card announces its question and the piece it produces. The workspace becomes a dimension — a column, a filter tag — and has its own chapter: Workspaces.

The scope is the subscription, its active workspaces. The two shelves are those of the Workspace Center, described in Reading the reports — with a difference in nature: the pieces are issued in each workspace, this console consults and exports them. We do not produce a "subscription" cover edition; we read, workspace by workspace, those that have been issued.

The report specific to this console: Workspaces

Where is each workspace, and which one is behind? And its warning, written on the card: compares entities of different sizes: sort by volume, bars at the subscription level, no overall rate — and a line for those below the threshold.

Three counters: Active workspaces in the scope, With campaign over the period, Below N% progress. Then a line per workspace: requests entered, decided, progress, resources, decided resources — and the label below N% for those lagging. A second section lists those without a campaign over the period: no requests: no progress to read, no delay either.

The phrase to remember is that of the report: No overall rate: a workspace of 40 resources and one of 4,000 are not read on the same scale. Each line carries its own progress; progress is not compliance.

The others, at this scale

Coverage, Decisions, Execution: the same sections as in the workspace, with a filter tag per workspace and one more column. Workload and delay and Roles and authorizations remain internal monitoring, hidden from the Auditor role. A workspace out of scope — deactivated, in the trash — is not counted, and the report says so.

03The status of services #sec_9c0be8ff

Supervision › Services — Subscription health status. The status of the processes that run your subscription. What you can handle yourself is in the Alert Center.

The page starts with a scan verdict, calculated at opening: The processes are all up to date. Nothing awaits a decision from you. Or: N processes out of N are up to date. …: nothing more produced since …. Or again: We could not read the status of N out of N processes — with the precision that matters: not being able to look does not mean everything is fine: this status is never filed under "up to date".

Then a line per process: its name in common language, its last observation, its status — Up to date, Delay observed, Out of scope, We do not know — and what it means. Out of scope is not a failure: this process is not installed on this subscription. Nothing awaits it here.

Relaunching a scan redoes the observation. Viewing the delayed process leads there.

What this page does not do

This page does not show any job name, any cadence, any instance, any version. It does not ask you anything either: the same report goes to the operator: the incident is opened on our side without you having to report it.

And it does not replace the Alert Center: open incidents, ongoing requests and what awaits a decision from you live in the Alert Center. Services says if the machine is running; the Alert Center says what you have to do.

04How to read the two together #sec_09d4e705

A workspace below the threshold in the Workspaces report has two possible explanations: its reviewers do not decide, or something is not running. Services resolves the second one in one page opening. If everything is up to date, the delay is human, and it is the workspace manager who should be called — with the Workload and delay report of his workspace.

05The rhythm #sec_3d357946

06To remember #sec_369e076a

Subscription reports read, they do not issue; the Workspaces report compares without ever giving an overall rate. Services observes the status of the processes and opens the incident for you — and when it does not know, it says so, instead of saying everything is fine.