Post an issue

Describe what you're seeing

Paste anything you have — a CLI/portal screenshot summary, a Terraform diff, an error message, a resource ID, or just a paragraph. We extract the cloud, resource type, and severity hints, then start enrichment as if a scanner had found it. No fields below are mandatory except a title.

STEP 1

Describe the issue

Title*What you saw (paste evidence)

Attachments (screenshots, JSON, CLI / PS output, Terraform, logs)

Drag & drop here, or . Up to 8 files, 25 MB each. Images, JSON, YAML, .tf, .ps1, .sh, .log, .txt.

STEP 2

Identify the resource (optional)

Resource idWe try to resolve this against the inventory. If we can't, the investigation still runs and asks for clarification.

STEP 3

Scope (helps narrow the search)

CloudSubscription / Account / ProjectEnvironmentCategory

STEP 4

Severity & context (engineer's gut)

Why are you concerned?

Severity (your view)Not used for ranking; the orchestrator computes a canonical severity once enrichment runs.UrgencyContext

STEP 5

Start the investigation

On submit: we save the issue, extract cloud/resource/category from your text, try to resolve the resource against the inventory, create an Investigation, and open the workspace. The extractor output is preserved so you can see exactly what we parsed.

Attachments upload directly to private blob storage via short-lived SAS URLs — the app server never sees the bytes. Per-tenant lifecycle: hot 0-30d, cool 30-90d, archived 90-365d, then deleted.