Dashboard Guide

The Operyn Console is the central interface for monitoring, investigating, and managing incidents. This guide walks through the key areas of the UI. Access to the console is controlled by authentication and roles and permissions.

Layout

The console is split into three main areas:

┌──────────────────────────────────────────────────────┐
│  Header (search bar, theme toggle, notifications,    │
│          docs sidebar, profile dropdown)             │
├────────┬─────────────────────────────────────────────┤
│        │                                             │
│  Side  │              Main Content                   │
│  bar   │                                             │
│        │                                             │
└────────┴─────────────────────────────────────────────┘

Sidebar

The left sidebar contains navigation links to all major sections:

Header

The header bar contains several interactive elements:

• Search Bar — click or press ⌘K to open the command palette.
• Theme Toggle — switch between light and dark mode.
• Notification Bell — shows a popover with recent alerts and an unread count badge.
• Docs Sidebar — press ⌘. to open the contextual documentation panel.
• Profile Dropdown — access profile, settings, and sign out.

Command Palette

Press ⌘K (or Ctrl+K on Linux/Windows) to open the command palette. It provides:

• Page navigation — quickly jump to any console section.
• Incident search — search incidents by title or ID.
• Documentation search — find docs without leaving the console.
• Quick actions — toggle theme, open settings, etc.
• Recent searches — your last queries are saved locally for fast recall.

Results are grouped by category (Recent, Pages, Incidents, Documentation, Actions) and support keyboard navigation with arrow keys.

Contextual Docs Sidebar

Press ⌘. (or Ctrl+.) to open the docs sidebar. It loads documentation directly within the console, so you can reference concepts without switching to a browser tab.

Features:

• Navigation list — browse all doc sections and pages.
• Full-text search — filter docs by keyword.
• Breadcrumb header — shows Section / Title when viewing a specific doc.
• External link — open the current doc in the full documentation site.
• Escape to go back — press Escape to return to the navigation list.
• Content caching — previously loaded docs are cached in-memory.

Incident Detail Page

Click any incident in the list to open its detail page. The detail view contains:

• Incident header — title, severity badge, status, affected services, timestamps.
• Environment context — the incident environment is shown directly and now flows through filtering and remediation policy checks.
• AI Diagnosis — root cause analysis from the AI Engine with confidence score.
• Timeline — chronological log of events, status changes, and comments.
• Remediation actions — proposed fixes with Approve / Reject buttons, decision reason capture, and policy context.
• Comments — add notes for post-incident reviews.
• Diagnostic probe — provider-aware, typed, read-only investigation tools (Kubernetes + AWS) with structured evidence.

Diagnostic Probe (Kubernetes + AWS)

The incident detail probe panel lets responders run safe investigation tools directly from the incident workflow.

• Provider-aware tool picker — choose Kubernetes or AWS diagnostic tools.
• Typed inputs only — no arbitrary shell or free-form command execution.
• Scoped execution — tools are validated against incident-scoped resources and organization policy.
• Structured results — each run returns summary + key patterns + output reference; raw output is not inlined into incident context.

Supported AWS tools in the first slice:

• getCloudWatchLogs
• getRdsHealth
• getAlb5xxMetrics
• getLambdaErrors
• getSqsBacklog
• getEcsServiceHealth

Use the API references for exact contracts:

• POST /incidents/:id/diagnostic-tools/run
• GET /incidents/:id/diagnostic-tools/runs
• GET /incidents/:id/diagnostic-tools/runs/:runId
• GET /incidents/:id/diagnostic-tools/metrics

Incident Resource Mapping

AWS diagnostic tools are deny-by-default until resources are mapped to the incident.

• Use the incident resource editor to map account/region/resource context.
• Keep mappings limited to resources directly involved in the incident.
• If mapping is missing or out of policy, tool execution is rejected with a validation error instead of running unsafely.

API references:

• GET /incidents/:id/resources
• PUT /incidents/:id/resources

Remediation Decision Details

When a suggested fix is gated by policy, the incident view and remediation queue show:

• Decision actor — who approved or rejected the action.
• Decision reason — the optional operator note entered during approval or rejection.
• Policy context — the exact rule or policy path that required approval, blocked the action, or allowed it to proceed.

This makes it easier to distinguish a human override from the original safety rule that triggered the review.

Notifications

Bell Popover

The bell icon in the header shows the 8 most recent high-severity alerts. Each item displays the title, service, severity, and time ago. Click any item to navigate to the incident.

Full Page

Navigate to Notifications in the sidebar for the complete notification feed. Use the filters to narrow by severity or show only unread items. The page follows the same high-density console layout as Analytics and Remediation so responders can scan recent activity quickly.

Integrations

Navigate to Integrations in the sidebar to manage inbound telemetry connections and organization-level outbound integrations. This page now lives at /console/integrations; the older /console/settings/integrations route redirects here for compatibility.

Use the page to:

• Connect ingestion sources such as AWS CloudWatch.
• Configure per-organization integrations such as Discord, Jira, and generic webhooks.
• Run test actions to validate integration wiring before rollout.
• Keep operational setup separate from the rest of workspace settings.

Settings

Navigate to Settings in the sidebar to manage workspace configuration. The settings section has four tabs:

General

Quick links to key configuration pages — Notification Channels, Team Management, Correlation Rules, and Safety Policies.

Notifications

View which notification channels (Slack, Discord, Jira, PagerDuty, Datadog, Grafana, Webhook) are connected. Each channel card shows its status and provides a Test button to send a test notification. All channels are configured via the Dashboard with encrypted-at-rest credentials.

See the Notification Channels Setup Guide for detailed instructions.

Team

Manage team members with roles and on-call status. You can:

• Add new team members (name, email, role).
• Toggle on-call status for each member.
• Remove team members.

Billing

Monitor your plan's usage and manage your subscription. The Billing tab shows:

• Current Plan: Information about your active tier (Starter, Pro, or Enterprise).
• Resource Usage: A progress bar showing how many services you're monitoring against your plan's limit.
• Manage Billing: A direct link to the Stripe customer portal for invoices and payment method updates.
• Available Upgrades: Upgrade your tier or switch between Monthly and Yearly billing intervals.
• Plan Features: A detailed list of what's included in your current subscription.

For more information on tiers, limits, and retention, see the Pricing & Billing concept doc.

Profile

View and update your personal information — name, email, timezone. Your role and on-call status are also displayed here.

Keyboard Shortcuts