Workspace Incidents
Disconnected

OBSERVE · INVESTIGATE · UNDERSTAND

Incident workspace

A clear view of your cloud events and the evidence behind them.

Read-only VM health adapters — diagnostic coverage is limited

Configured adapters support Azure VM and AWS EC2 health checks only. Full RCA, logs, and metrics are not supported yet. Reports are preliminary and do not establish a verified root cause. No remediation is performed.

Total reports—Reported by the service
High severity—In the latest loaded reports
Evidence gaps—Reports with missing evidence
Service readinessChecking…Storage: checking…

Cloud connections

Configured Azure VM and AWS EC2 read-only adapters.

Cloud credentials stay on the server, using server secrets or an AWS instance role. Never enter cloud credentials here. Verification validates identity; discovery and health investigation run only when you select their controls.

Recent incidents

Connect to load the latest 50 reports.

Your investigations start here

Connect with a bearer token to explore reports or submit a normalized event.

No reports loadedTemporary report cache

INVESTIGATION

Report details

VM health only

Select an incident

Explore findings, supporting evidence, and what still needs to be investigated.

WORKSPACE ACCESS

Connect to your service

Enter your operator token to access reports and cloud connections. The token is held only in memory and cleared when you disconnect or reload. In development, the service may use one shared token for operator access and event submission.

Enter the token only, without the “Bearer” prefix. Production event submission uses a separate webhook token in the event form.

NORMALIZED INPUT

Submit a cloud event

Create a preliminary report from a compact event. Include relevant context; avoid secrets and raw telemetry.

Production uses a separate webhook token to submit events. Enter the token without the “Bearer” prefix. Leave blank to use your connected token for the development fallback. This token is used only for this submission and cleared as the request starts or when this dialog closes.

The service timestamps this event when received. No cloud commands or remediation are executed.