Dashboard
Real-time command center providing fleet health, governance compliance, and operational awareness at a glance.
Overview
The dashboard is the first screen you see after login. It serves as a real-time command center that surfaces the health, readiness, and operational state of your entire GitOps operation. Rather than forcing you to drill into individual projects or clusters, the dashboard aggregates the most critical signals into a single view.
The dashboard answers four questions at a glance:
- Are my projects ready to deliver? — Project readiness score
- Are my clusters healthy? — Fleet connectivity status
- Am I in compliance? — Governance violation resolution rate
- What happened recently? — Activity pulse and audit entries
KPI Metrics Section
The top of the dashboard displays four key performance indicator cards. Each card shows a current value, a trend indicator, and a contextual label.
Project Readiness
Measures the percentage of projects that are fully operational. A project is considered "ready" when its project.initialized flag is true. This flag is set when the hosted Git repository is created and InitializeGitOpsStructure has run successfully.
Formula: (initialized projects / total projects) × 100
A readiness score below 100% indicates projects that were created but whose Git repository has not yet been initialized. These appear in the Attention Signals section.
Fleet Health
Shows the connectivity status of all registered clusters across the organization. Thresholds are derived from statusIntervalSeconds (default 30 seconds).
| Status | Meaning |
|---|---|
| Healthy | Agent heartbeat age is within 2x the base interval (default: 60 seconds) |
| Lagging | Agent heartbeat age is within 10x the base interval (default: 300 seconds) |
| Offline | Agent heartbeat age exceeds 10x the base interval |
Formula: (healthy clusters / total clusters) × 100
A fleet health score below 100% requires immediate investigation. Offline clusters cannot receive deployments or report drift status.
Governance Resolution
Tracks how effectively your organization resolves policy violations. Policy violations are generated when:
- A deployment proceeds without required approval
- A break-glass session is used (requires post-incident review)
- A configuration change violates an organizational policy
Formula: (resolved violations / total violations) × 100
A 100% resolution rate means all violations have been acknowledged, reviewed, and closed.
Registry Footprint
Displays the total count of reusable artifacts in your organization's catalog:
- Charts: Helm chart versions in the registry
- Kustomize Bases: Kustomize configuration versions
- Manifest Bundles: Raw manifest collection versions
This metric helps you track the growth and utilization of your shared artifact catalog.
Attention Signals
Below the KPI cards, the dashboard highlights issues that require immediate action. Each signal includes a count, a severity indicator, and a direct link to the relevant resource.
Offline or Lagging Clusters
Clusters whose agents have disconnected or are reporting stale heartbeats. Each entry shows:
- Cluster name and provider
- Last heartbeat timestamp
- Time since last contact
- Direct link to cluster detail page
Unresolved Policy Violations
Open governance violations that have not been reviewed or resolved. Each entry shows:
- Violation type and description
- Affected resource (project, environment, release)
- Creation timestamp
- Direct link to the violation detail
Uninitialized Projects
Projects that were created but have not completed setup. Common reasons:
- Hosted repository not yet initialized
- No environments configured
- No workloads defined
Each entry links directly to the project setup wizard.
Unbound Clusters
Clusters that are registered and connected but are not targeted by any project environment. These clusters are consuming agent resources without serving any delivery purpose.
Attention signals are computed in real time. Resolving the underlying issue removes the signal from the dashboard automatically.
Environment Matrix
The environment matrix provides a projects × environments grid view showing deployment status at every intersection.
Reading the Matrix
| Column | Content |
|---|---|
| Rows | One row per project |
| Columns | One column per org environment (ordered: dev → staging → production) |
| Cells | Deployment status indicator for that project-environment pair |
Cell Status Indicators
GetDashboardMatrix populates each cell with a syncStatus field. For most cells this value is "unknown" because the matrix query does not join full ArgoCD sync/drift data by default. The frontend may enrich cells with additional API calls, but out of the box the matrix primarily indicates whether a project-environment combination exists rather than conveying real-time sync health.
| Indicator | Meaning |
|---|---|
| Filled circle | Project-environment combination exists |
| Gray circle | Environment not configured for this project |
| Dash | No deployments exist for this project-environment |
Clicking a cell navigates to the project's environment detail page where you can inspect individual tenant statuses with full drift and sync information.
Provider Breakdown
A visual distribution showing how your clusters are spread across cloud providers and regions.
| Provider | Examples |
|---|---|
| AWS | EKS clusters |
| GCP | GKE clusters |
| Azure | AKS clusters |
| On-Prem | Self-managed Kubernetes |
| Other | k3s, kind, custom distributions |
This breakdown helps platform teams understand their infrastructure distribution and plan capacity accordingly.
7-Day Activity Pulse
An activity strip spanning the past seven days. Each day shows:
- Deployment count: Number of successful deployments
- Release count: Number of releases created and deployed
- Command count: Number of cluster commands executed (sync, rollback, restart)
- Incident markers: Days with policy violations or failed deployments
The activity pulse provides a quick visual indicator of operational tempo. A sudden spike may indicate a major rollout; a sudden drop may indicate an environment freeze or holiday period.
Recent Audit Entries
The bottom section of the dashboard shows the most recent audit log entries across the organization. Each entry includes:
| Field | Description |
|---|---|
| Timestamp | When the event occurred (relative time, e.g., "3 minutes ago") |
| Actor | Who performed the action (user email or service account name) |
| Action | What happened (e.g., release.created, cluster.command.sync, member.role.changed) |
| Resource | The affected resource with a direct link |
| Details | Additional context (e.g., release version, target environment) |
| Action | Description |
|---|---|
release.created | A new release was created |
release.approved | A release was approved by an approver |
release.deployed | A release was deployed to an environment |
release.rolled_back | A release was rolled back |
delivery.generated | The delivery generator produced new manifests |
| Action | Description |
|---|---|
cluster.registered | A new cluster was registered |
cluster.agent.connected | An agent established connection |
cluster.agent.disconnected | An agent lost connection |
cluster.command.sync | A sync command was sent |
cluster.command.rollback | A rollback command was sent |
| Action | Description |
|---|---|
member.invited | A new member was invited |
member.role.changed | A member's role was updated |
team.created | A new team was created |
grant.assigned | A permission grant was assigned |
service_account.token.created | A new service account token was generated |
Clicking "View All" navigates to the full audit log with advanced filtering and search.
Navigation and Quick Access
The dashboard provides quick-access links to primary sections:
| Section | Description | Keyboard Shortcut |
|---|---|---|
| Projects | All projects in the organization | G then P |
| Clusters | All registered clusters | G then C |
| Registry | Helm charts, Kustomize bases, manifest bundles | G then R |
| IAM Center | Members, teams, service accounts, grants | G then I |
| Tenants | Organization tenant registry | G then T |
| Settings | Organization settings and billing | G then S |
Command Palette
The command palette is accessible from anywhere in GitOpsHQ via Cmd+K (macOS) or Ctrl+K (Windows/Linux).
Capabilities
| Category | Examples |
|---|---|
| Navigate | Go to a project, cluster, tenant, or settings page |
| Search | Find resources by name across all resource types |
| Actions | Create a release, register a cluster, invite a member |
| Recent | Jump to recently visited pages |
The command palette supports fuzzy matching — typing "prod cluster" will surface production-targeted clusters even if the exact name differs.
The command palette indexes all resources in your organization. Results are filtered by your current permissions — you only see resources you have access to.
Dashboard Refresh Behavior
| Data | Refresh Method | Interval |
|---|---|---|
| KPI Metrics | Automatic polling | Every 30 seconds |
| Attention Signals | Automatic polling | Every 30 seconds |
| Environment Matrix | Automatic polling | Every 60 seconds |
| Activity Pulse | Page load + manual refresh | On demand |
| Audit Entries | Automatic polling | Every 15 seconds |
The dashboard does not use WebSocket connections. All data is fetched via standard HTTP polling to ensure compatibility with corporate proxies and firewalls.
Related Pages
- Core Architecture — Understand the overall system design
- Drift Detection — Deep dive into drift indicators shown on the dashboard
- Tenant Management — Manage the tenants shown in the environment matrix