Observability Module
Version 2025‑05‑16
Table of Contents
Introduction
Conscia’s DX Engine sits between your front‑end and every back‑end service, orchestrating real‑time API calls, caching, and business logic.
Because it is the connective tissue of your composable stack, first‑class observability is critical.
Observability Architecture
Application ──▶ DX Engine (Query Node)
├─ Component or Flow Execution
└─ Events Emitted at Request and Component Level
├─ Analytics Aggregator
└─ Webhook Router
- Every Experience API call receives a Request ID.
- Component and Flow executions emit events and generate structured logs with details on response,
@debug
,@extras
, performance metrics). - Logs feed both real‑time dashboards and Webhook / external SIEM targets (Datadog, New Relic, Elastic, etc.).
Observability Dashboards
All dashboards share common controls:
- Select Dashboard — choose high‑level Request metrics or granular Component metrics.
- Time Range — dual date‑time pickers.
- Flow / Component Picker — multi‑select with type‑ahead.
- Submit — run the analytics query.
Flow-Level Request Details Dashboard

Chart | Insight |
---|---|
Average Request Duration by Flow (pie) | Which flows contribute most to aggregate latency. |
Average Request Duration by Flow (line) | Latency trend (ms) — zoom slider for spikes. |
Number of Requests by Flow (pie) | Traffic distribution. |
Requests Over Time (line) | RPS per flow; correlate traffic vs latency. |
Component-Level Request Details | Status Dashboard

Widget | Insight |
---|---|
Executions by Status (pie) | Ratio of VALID , SKIPPED , FAILED . |
Failed Executions (Sample) | Hyper‑links to Request ID and Component Execution ID for debugger drill‑down. |
Component Details | Status
This dashboard provides the breakdown of status codes when a Component is selected. It also provides the list of the most recent failed executions.

Additional Tooling
Tool / View | Purpose |
---|---|
Execution Analysis | Run live or mock queries; inspect dependency tree, component states, context enrichment, cache hits. |
Query Request History | Audit trail of past Experience API calls - search for a specific Request ID. Note that this is currently available via the API |
Execution Analysis
Here is the screenshot for a sample Execution Timeline that provides details of how the DX Engine processes each component or flow level request.

Roadmap
- Ability to set triggers for certain incidents. For example, greater than 5 errors in 10 minutes for Component A.