Performance

Overview#

A 999 dispatcher cannot afford a sluggish interface when seconds matter. The Performance domain monitors response times, frontend Core Web Vitals, and emergency-specific metrics such as alert processing and evidence upload times, then alerts the team before degradation reaches users. Synthetic tests run continuously across regions so problems surface in controlled conditions, not during a real incident.

Key Features#

Request/response metrics including duration, throughput, and error rate tracking
System resource monitoring for CPU, memory, disk, and network I/O
Core Web Vitals tracking: LCP, FID, CLS, INP, and TTFB
Law enforcement-specific metrics for emergency response, alert processing, and evidence upload times
Configurable performance budgets with percentile-based targets and violation thresholds
Multi-region synthetic monitoring with scenario-based testing
Budget violation tracking with user and business impact scoring
Performance analytics with trend analysis, regional comparisons, and optimisation recommendations
Real-time dashboard data with overall health scores and active incident counts
Automated alerting with escalation levels for critical performance degradation

Use Cases#

Relevant sectors include law enforcement, critical infrastructure, and intelligence operations.

Monitoring emergency dispatch response times to ensure compliance with service-level targets
Detecting and resolving performance degradations before they impact field operations
Running synthetic tests across regions to validate system responsiveness under load
Tracking Core Web Vitals to maintain optimal frontend performance for investigators

Integration#

The Performance domain integrates with observability, health monitoring, alert management, and analytics systems. It supports real-time dashboards and automated alerting workflows.

Open Standards#

W3C Core Web Vitals: LCP, FID, CLS, INP, and TTFB are first-class metric types, using the thresholds and definitions published by the W3C Web Performance Working Group.
GraphQL (June 2018 specification): All performance data queries, budget management, and synthetic monitoring results are exposed through a typed GraphQL API.
W3C Trace Context: Each recorded metric carries a traceId field correlated against the platform's W3C Trace Context middleware, enabling end-to-end distributed trace lookup.
OpenTelemetry Protocol (OTLP): The platform exports traces to an OTLP-compatible backend (Tempo/Jaeger), and trace identifiers recorded in performance metrics link directly into that pipeline.
ISO 8601: All metric timestamps, budget windows, and query time ranges are serialised and parsed as ISO 8601 date-time strings with explicit UTC offset.
ISO/IEC 9075 SQL (ordered-set aggregates): p50, p95, and p99 latency percentiles are computed using PERCENTILE_CONT … WITHIN GROUP as defined in SQL:2003 and later editions.
OAuth 2.0 / JSON Web Tokens (RFC 7519): Every GraphQL query and mutation resolves a current_user derived from the platform's JWT-based bearer-token authentication before any performance data is read or written.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14