Skip to content

Operations

Operations covers the two live operating views in SLApulse:

  • Health Monitor
  • Triage Board

Use these views after Command Center shows that one or more projects are ready for live monitoring.

Operations is for day-to-day SLA work. Members and Admins can both use it. Configuration changes that affect Operations, such as source setup, SLA rules, users, and billing, belong in the Admin-only Setup area.

Operating flow

The normal operating flow is:

  1. Open Command Center to see which projects need attention.
  2. Open Health Monitor to read the workspace vital signs.
  3. Use Triage Board to work issues by urgency, or choose Open shared display for a team screen.
  4. Open Analysis when you need detail, timeline evidence, exports, or historical compliance.

Health Monitor

Health Monitor is the live risk overview for the workspace. It answers one question: where is the SLA risk now? Use it to understand the current pressure, then use Triage Board when a signal needs work.

It shows:

Signal Meaning
Health score Percentage of all monitor issues, active and paused, that are not T1 or T2.
Active issues Current active monitor issues and the number of projects they span.
Critical · T1–T2 Monitor issues that need prioritisation.
Paused Monitor issues whose SLA time is not currently counting down.

When there are T1 or T2 signals, Next action names the two most urgent issues by consumed SLA budget and provides the page's only action: open Triage Board. When there are no T1 or T2 signals, this panel is not shown.

The page refreshes automatically every 15 seconds while the browser tab is active. When the tab is hidden, it checks every 60 seconds to reduce unnecessary work. Remaining time continues to update between checks. If a later refresh fails, the last successful live overview remains visible while SLApulse tries again.

Triage distribution

The distribution shows all active and paused monitor issues across the five triage levels. Each level keeps a text label and a count, including zero-count levels, so the overview does not rely on colour alone. An empty monitor set is explained instead of showing a blank chart.

Level Meaning
T1 Critical. Immediate intervention is needed.
T2 Severe. Work should be prioritized now.
T3 Moderate. Monitor actively and handle before deterioration.
T4 Stable. Work is currently under control.
T5 Healthy. No immediate SLA pressure.

Use the distribution to understand whether pressure is concentrated in a few critical issues or spread across many moderate issues.

Active alerts

Active alerts repeat the same two highest-priority T1/T2 signals from Next action as passive information. They show the issue key, source priority, triage level, consumed SLA budget, and remaining time.

Paused alerts are marked clearly and their remaining time does not count down. The list deliberately has no issue links or extra buttons; open Triage Board when you need to work the queue.

SLA pulse

SLA pulse shows the current SLA status for each monitored project in a two-column overview. Each project box shows its Health score, worst current triage level, and counts for active, critical, and paused issues.

The small pulse mark is a current status marker, not a history curve. This keeps the overview focused on what needs attention now; use Analysis when you need timeline evidence or historical compliance.

Triage Board

Triage Board is the calm working surface for active and paused issues. Start by reading the T1 column, then move through the board in priority order. Each of the five T1-T5 columns keeps its level, meaning, count, and colour visible, including when a level has no issues.

The distribution panel counts active and paused issues in the selected scope. It also shows when the server last supplied a successful check. While the first check is loading, or when it cannot be completed, the board explains that state instead of presenting an empty board as current data.

Within a column, active issues appear before paused issues. Each group is sorted by consumed SLA budget, with the highest pressure first. The first visible issue is open initially. Open another card with its built-in disclosure to read which SLA dimension is driving the pressure, its current percentage and remaining time. The explanation is read-only: it does not open issue details or request history.

Use filters when you need to narrow the board:

Filter Use it when
Project A team is responsible for one project or customer.
Priority You need to focus on a specific source priority.

The selected scope is stated beside the filters. When either filter is active, choose Reset filters to return to the full board without reloading the page. Choose Open shared display to open the current filtered view in a new kiosk tab. The filters include both active and paused issues.

Paused issues can still appear because a paused SLA may need follow-up if it has waited too long or blocks the customer path. They are marked as paused, and their remaining SLA time stays fixed until the SLA clock resumes. Active remaining time continues to count down between automatic checks.

The board refreshes automatically every 15 seconds while the browser tab is visible and every 60 seconds while it is hidden. If a later check fails, the most recent successful board stays visible.

Kiosk mode

Kiosk mode is a separate shared-display view without the app navigation. From Triage Board, choose Open shared display to open it in a new tab with the current project and priority filters. You can save that tab's address for the same shared display later.

You can use kiosk mode with all projects, one project, one priority, or both filters. The board keeps the selected filters when the tab becomes active or hidden, and the displayed SLA time stays current between refreshes.

In kiosk mode:

  • F toggles fullscreen
  • Esc exits fullscreen and returns to the normal Triage Board with the selected filters intact
  • cards are compact and read-only, so the screen stays focused on the shared queue

Use kiosk mode for team rooms, service desks, and operational displays where the goal is visibility rather than detailed investigation.

When to use Analysis instead

Operations is for deciding what to work on now.

Open Issues in the Analysis area when you need the detailed chart:

  • lifecycle timeline
  • full event history
  • SLA explanation
  • source status detail
  • destructive issue delete action

Open Reports in the Analysis area when you need historical compliance, export, or contract follow-up.