Skip to main content

Dashboard Usage

The dashboard is like the "cockpit" of KIOPS. Just as a pilot checks all the instrument panels in the cockpit, you can check the status of all your services at a glance from the dashboard.

The dashboard is a monitoring-only screen

The [Dashboard] has no tab layout. It consists of a single service status table. Action buttons such as build, deploy, and restart are not available on the dashboard. Those actions are performed on the service detail page or on the Service Management page.

Accessing the Dashboard​

Path: [Dashboard] page (/dashboard)

This is the first screen you see after logging in. You can check the status of all services in a single table.

Screen Layout​

The dashboard page is composed as follows:

  • Top area: Search/filter inputs (there is no manual refresh button; data is updated via WebSocket in real time plus auto-load)
  • Main area: Service status table (single screen)
  • Status indicator: A disconnect indicator is shown at the top when the WebSocket connection drops

Service Status Table​

The heart of the dashboard is the service status table. Here you can see all service statuses at a glance and click a row to enter the detail page.

Columns​

The columns actually rendered in the table are:

  • Favorite (star icon): Star a service to favorite it. Favorite state is stored in the browser's localStorage (persisted per browser) and favorited rows are sorted to the top.
  • Service Status: Pipeline stage status (Running, Building, Deploying, Build Failed, Deploy Failed, Stopped, Registered, etc.) shown as colored badges.
  • Risk Level (riskLevel): Auto-computed label based on vulnerability counts. (See the section below for the calculation rules.)
  • Service Name: The registered service name.
  • Branch: A dropdown showing the currently monitored branch. You can switch to another branch directly.
  • Runtime Environment: The name of the runtime where the service is deployed (K8s cluster, Docker, Podman, etc.).
  • VPN: VPN profile used to reach this service.
  • Navigation (arrow icon): Clicking it switches to the service detail page (ServiceDetailView).
There is no Build/Deploy/Restart "Actions" column

The dashboard table does not include an action button column. Build, deploy, and restart are performed on the service detail page or on the [Service Management] page.

How riskLevel Is Computed​

The risk level label is derived automatically from the service's vulnerability statistics and falls into four tiers (critical/high/medium/low).

  • critical: At least one Critical vulnerability exists
  • high: No Critical, but at least one High vulnerability exists
  • medium: No Critical/High, but at least one Medium vulnerability exists
  • low: Medium, High, and Critical counts are all zero (regardless of any Low vulnerabilities)

Colors are applied based on these four tiers so it is easy to spot at a glance.

Understanding Service Status​

Each service is displayed in a different color based on its current pipeline status.

  • Running: Service is running normally.
  • Building: Build in progress. Please wait.
  • Deploying: Deployment in progress.
  • Build Failed: Build failed. Check the logs on the detail page.
  • Deploy Failed: Deployment failed.
  • Stopped: Service is stopped.
  • Registered: Only registered; build/deploy has not been run yet.

When you have many services, use the search/filter inputs in the top area to narrow down.

  • Status / risk level filter: Show only services in a particular status (e.g., Failed) or risk level (e.g., critical/high).
  • Search: Substring search by service name.
Morning check tip

Right after you start work, apply the critical/high risk filter or the Failed status filter first. This narrows the list to only the services that need immediate attention.

WebSocket Real-Time Updates​

The dashboard table reflects pipeline status changes in real time via WebSocket.

  • Build/deploy progress, completion, and failure updates appear without a manual refresh.
  • If the WebSocket connection drops, a disconnect indicator appears at the top. Wait for the indicator to clear or refresh the page if status updates seem delayed.

Service Detail Page (ServiceDetailView)​

Clicking a service in the table or the navigation icon transitions to ServiceDetailView. This is an SPA transition within the dashboard screen, not a route change. Use the back button in the top left to return to the table view.

The detail page is a single Overview screen with no tabs.

Overview Screen​

Shows the service's current state and recent activity.

  • Basic service info (name, runtime environment, VPN, branch, etc.)
  • Recent build/deploy history summary
  • Current operation status (Running/Stopped/etc.)

Quality metrics moved to the [Quality] tab of [Security Analysis]​

DORA metrics, incidents (failure history), and the security vulnerability summary are no longer shown on the dashboard service detail. View them in the [Quality] tab of the [Security Analysis] page (/security?area=quality). (Note: these are per-service metrics, not system-wide.)

  • DORA Metrics: Deployment frequency, lead time, change failure rate, time to restore. See the DORA Metrics guide for details.
  • Incident History: List and status (Open/Resolved) of incidents auto-created on build/deploy failure. KIOPS records failures automatically, so you can trace failure history without any manual registration.
  • Security Vulnerability Summary: Vulnerability statistics derived from SAST/SCA/DAST scans.
Incident handling flow
  1. In the [Quality] tab of [Security Analysis], find incidents in Open state.
  2. Open the incident to review error logs and related build/deploy info.
  3. After fixing the root cause (code fix, config change, etc.), change the incident status to Resolved.

Real-World Usage Scenarios​

Scenario 1: Morning Status Check​

The first thing you should do every morning when you arrive at work.

Check sequence:

  1. Access the [Dashboard] page.
  2. In the top filter area, select critical/high in the risk level filter, or Failed in the status filter.
  3. If any rows remain, click the navigation icon on that row to enter the detail page.
  4. Check recent build/deploy results on the Overview screen, then review incident details in the [Quality] tab of [Security Analysis] if needed.
  5. After fixing the issue, run a rebuild or redeploy from the [Service Management] page.

Scenario 2: Favorite-Based Monitoring of Core Services​

If you operate many services, use favorites to keep your core services on top.

  1. Click the star icon on the left of a core service row to favorite it.
  2. Favorited services are sorted to the top.
  3. The favorite state is stored in localStorage and persists across reloads in the same browser.

Scenario 3: Security Risk Review​

The risk level labels give you a quick picture of vulnerability distribution.

  1. Apply the critical filter to surface services that need immediate action.
  2. Review the security vulnerability summary for the service in the [Quality] tab of [Security Analysis].
  3. Address higher-priority vulnerabilities first, then rerun the security analysis to confirm resolution.

Best Practices​

Daily Routine​

Check three times a day

Morning, midday, and end of day. Just these three checks are enough to catch most problems quickly.

  • Morning: Scan service status and risk level labels. Catch overnight issues early.
  • Midday: Open the notification drawer and review newly arrived pipeline alerts.
  • End of day: Check for Failed statuses and Open incidents.

Weekly Routine​

Team-level checks for improvement.

  • Monday: Review DORA metrics in the [Quality] tab of [Security Analysis] for your key services to analyze last week's DevOps performance.
  • Friday: Reflect on incidents from the week and discuss prevention measures.
Good habits produce good results

It may feel cumbersome at first, but once these routines become habit, you'll be able to discover problems early and respond quickly.