Skip to main content

Sector Dashboards

Sector Dashboards show where risk is rising across sectors such as finance, energy, healthcare, and other monitored areas. Use this page as an early-warning view before deciding whether a deeper response workflow is needed.

Workspace route: #/sector-dashboards

What You See​

  • Overview: the current anomaly score, alert state, number of signals, and number of affected sectors.
  • Pressure: ranked sectors and the strongest signals behind the current pressure.
  • Capacity: workflow and memory headroom before running more automation.
  • Memory: saved workflow pointers from previous response runs.
  • Quality: drift and decision quality checks.
  • Simulation: deterministic replay coverage for systemic anomaly logic.
  • Healing: self-heal, performance, and security posture checks.
  • Workflow: response workflow status, approval, retry, rollback, and EvidencePack (Dralvia's exportable evidence report) actions.

Where Data Comes From​

The page reads the latest systemic-anomaly snapshot from:

  • GET /api/autonomous/systemic-anomaly/sector-dashboard

Snapshots are created when your workspace submits real systemic-anomaly signals or when an operator runs the built-in sample detection from the UI.

This page is not packet capture and does not inspect raw network traffic by itself. It summarizes signals already available to Dralvia.

First-Time Walkthrough​

  1. Open #/sector-dashboards.
  2. Start on Overview to check whether the alert state is normal or elevated.
  3. Open Pressure to see which sectors and signals are driving the score.
  4. Open Capacity before starting heavier response automation.
  5. Use Workflow only when you want a governed response run with evidence.

How To Read It​

  • High pressure plus upward movement means investigate first.
  • High pressure without movement means monitor and prepare mitigation.
  • Low pressure with upward movement means add it to the watchlist.

Common Issues​

  • If there is no data, run sample detection once or wait for real signals to arrive.
  • If buttons are disabled, confirm your account has the required role and that the feature is available for your plan.
  • If a workflow fails, use Workflow to refresh status, retry eligible runs, or collect an EvidencePack for support.

Who this is for​

This page is for security operators, analysts, and incident leads who want an early read on where cross-sector risk is rising before committing to a deeper response workflow.

Role-based start here​

  • Analyst / operator: start on Overview, then Pressure to see what is driving the score.
  • Incident lead: use Capacity before heavier automation and Workflow for a governed response run with evidence.
  • Admin: confirm roles and plan availability so the team can use the response actions.

Before you start​

You need a workspace account with the required role and a plan that includes the sector dashboard. Either real systemic-anomaly signals submitted by your workspace, or one run of the built-in sample detection, so a snapshot exists to read.

Step-by-step​

  1. Open #/sector-dashboards.
  2. Read Overview to see whether the alert state is normal or elevated.
  3. Open Pressure to find the sectors and signals behind the current score.
  4. Check Capacity before starting heavier response automation.
  5. Use Workflow only when you want a governed response run with an EvidencePack.

Day-2 operations​

  • Check the alert state at the start of each shift and after major events.
  • Keep an eye on Pressure movement: rising pressure is the cue to investigate.
  • Watch Capacity so automation runs only when there is headroom.
  • Use Quality and Healing to confirm decision quality and posture stay healthy over time.

Self-check playbook​

  • Confirm a recent snapshot is present (run sample detection once if not).
  • Confirm Overview numbers match what Pressure shows.
  • Confirm response buttons are enabled for your role.
  • Run one governed Workflow action and confirm an EvidencePack is produced.

What each button does​

  • Overview / Pressure / Capacity / Memory / Quality / Simulation / Healing tabs: switch between the read-only views described in What You See.
  • Workflow actions: approve, retry, roll back, or refresh a response run.
  • Collect EvidencePack: produces a verifiable evidence artifact for the current response run.
  • Run sample detection: seeds a snapshot when no real signals have arrived yet.

Troubleshooting​

  • No data: run sample detection once, or wait for real signals.
  • Disabled buttons: confirm your role and that the feature is in your plan.
  • Workflow failed: refresh status in Workflow, retry eligible runs, or collect an EvidencePack for support.
  • Score looks stale: snapshots update when new signals arrive; confirm signals are being submitted.

API and automation​

  • The page reads GET /api/autonomous/systemic-anomaly/sector-dashboard for the latest snapshot.
  • Snapshots are created when your workspace submits real systemic-anomaly signals or when an operator runs sample detection.
  • This page summarizes signals already available to Dralvia; it is not packet capture and does not inspect raw network traffic by itself.

Next best actions​

FAQ​

Why is there no data on first open?​

No snapshot exists yet. Run sample detection once or wait for real signals to arrive.

Does this inspect raw network traffic?​

No. It summarizes systemic-anomaly signals already available to Dralvia, not raw packets.

Why are some actions disabled?​

Either your role does not have access, or the feature is not included in your plan.

Next steps​

API error quick reference​

Use this matrix when a UI action or API call fails with an HTTP error.

ErrorMeaningWhat to do now
401 UnauthorizedSession token or API key is missing, expired, or not authenticated.Sign in again (or refresh your API key) and retry in the correct workspace.
403 ForbiddenAuthenticated, but your role or plan does not allow this action.Confirm your role and that your plan includes the feature. Ask a workspace admin to grant access.
404 Not FoundThe route or resource does not exist in the current workspace context, or the feature is not enabled.Confirm the route, workspace context, and feature availability, then retry.
429 Too Many RequestsA rate limit or plan quota window was exceeded.Wait for the reset window, retry once, then reduce burst volume or upgrade the plan.
500 Internal Server ErrorThe backend failed unexpectedly while processing the request.Retry after 30 to 60 seconds. If it persists, escalate with workspace ID, UTC time, route, and error text.

Known limits and rate limits​

  • Plan quotas apply: scan, render, report, repository, and API-key limits follow your plan tier. See Pricing & Plans for the enforced defaults.
  • API requests are rate limited per workspace. A 429 Too Many Requests response means a rate or quota window was exceeded; wait for the reset window, then retry once and reduce burst volume.
  • Free Evaluation has the tightest limits and is subject to anti-abuse controls. Paid plans raise the limits; Enterprise sets custom limits by contract.