Skip to main content
Enterprise test automation and API orchestration require deep, actionable visibility into execution performance, error trends, and SLA violations. Quixa integrates directly with Metabase, streaming high-resolution execution telemetry from its relational store into pre-built executive and engineering dashboards.

​
1. Relational Telemetry Schema

Every execution on the Quixa visual canvas or through scheduled suites streams detailed performance metrics into dedicated SQL Server tables:
  • FlowExecution: Execution ID, Flow ID, Tenant, User, Status (Success, Failed, Aborted), Total Duration (ms), Start/End timestamps.
  • NodeExecution: Node ID, Node Alias, HTTP Method, Endpoint, Status Code, Latency (ms), Assertion Results, Retry Count.
  • FlowExecutionStep: Chronological execution logs and error diagnostics.

​
2. 1-Click Platform Admin SSO

To access Metabase without managing redundant credentials, Quixa provides seamless administrative Single Sign-On:
  • Endpoint: GET /api/analytics/metabase-sso
  • Mechanism: Authenticates the active PlatformAdmin or Admin JWT bearer token, creates secure metabase.SESSION cookies, and redirects directly into the Metabase console.
  • Embedded Views: Embedded dashboards inside the Quixa UI leverage signed, time-limited JWT tokens for static embedding without exposing database connection strings.

​
3. Pre-Built Dashboards

Quixa ships with pre-configured analytics dashboards out of the box:

​
1. Execution Overview Dashboard

  • Total runs across 24h / 7d / 30d.
  • Global pass/fail ratios and SLA adherence percentages.
  • Active flow suites and cron run distribution.

​
2. Latency & Performance Heatmaps

  • P50, P95, and P99 latency benchmarks across all endpoints.
  • Slowest downstream microservices identified by average response duration.

​
3. Failure Root Cause Matrix

  • Breakdown of HTTP 4xx vs 5xx error distributions.
  • Endpoints with recurring assertion failures.

​
4. Automated Error Threshold Alerts

Teams can configure automated threshold monitors:
  • Rule Example: If the suite failure rate exceeds 10% within any 30-minute window, trigger an automated incident.
  • Channels: Instant notification dispatch via Webhooks to Slack, Microsoft Teams, PagerDuty, or email distributions.