qdash ingests qcontrol's live event stream and exports findings locally — both work today. Outbound connectors are projected; each shows the real local volume it would carry. qdash binds 127.0.0.1 — nothing leaves unless you export it.

Connectors

Projected outbound destinations — each shows the real local volume it would carry.

Sources & enrichment

Bring identity and ownership context into qdash. Sources enrich locally — nothing is sent.

Okta / Entra IDWould match 14 observed harness identities against your IdP

Security & observability

Investigate qdash activity alongside your SIEM and observability stack.

Wh

Custom webhook active

21high routed

config

SplunkWould stream 48k events + 22 findings

Microsoft SentinelWould stream 22 findings + 37 egress destinations

Notifications & response

Alert teams or open incidents where people already respond. Severity routing here is consumed by Alerts.

Slack active

21high routed1medium routed

config

PagerDutyWould page on 21 high-severity findings

@

Email digestWould digest routed findings on a daily schedule

View All (4)

Remediation tracking

Turn findings into owned, trackable work for remediation.

JiraWould open tickets for 22 findings

Evidence & compliance

Retain evidence for audit, GRC analytics, and reporting.

Amazon S3 (Iceberg)Would archive 48k append-only events

SnowflakeWould land 22 findings for GRC analytics

S+

S3-compatible storageWould archive 48k append-only events to your own object store

qdash binds 127.0.0.1 and stores everything append-only in local SQLite. Outbound connectors are projected and off by default — the counts describe local readiness, not transmitted volume. Alert-channel severity routing is authored on each connector's page and consumed by Alerts.

Notifications

2 of 4 connected

Where findings go, by severity. A channel takes the findings whose severity it sends.

Channel	Sends	Status
Slack #sec-alerts	highmedium	Connectedlast delivery 11:40
{ } Custom webhook alerts.example.com/qdash	high	Connectednothing delivered yet
PagerDuty on-call	highwhen connected	Not connected Connect
Microsoft Teams Posts selected findings to a channel	—	Not connected Connect