Performance Overview

Track application activity, API response times and database load.

DEMO DATA
Sample data — not connected to production
Quest SQL Utilisation▤
—
Awaiting data
API Requests⇄
—
Requests in selected period
Slow Requests◷
—
Duration above 2 seconds
API Errors!
—
HTTP 5xx responses

Azure SQL Load Trend

QuestData — DTU %
DTU percentage by timestamp (independent of user-level API counts)

Load by Application

API request volumes
Request count is not actual database resource consumption. Use query tracing to attribute expensive work.

Top Users by Workload

UserApplicationRequestsAPI time

Recent Incidents

User & Transaction Investigator

Sample transactions or configured telemetry

Search a user ID, transaction ID, or trace ID. Traces must be collected and correlated by your backend.

TransactionUserApplicationActionDurationOutcomeTrace

Trace Timeline

Illustrative in demo mode
Select a transaction above to display trace spans.
Root cause must be supported by recorded trace spans, exceptions, SQL waits or VM telemetry. Correlation alone does not prove causality.
Sorted by cumulative API duration, not proven SQL load

Most Active / Costly Users

Click a row for activity details
UserRoleApplicationRequestsAPI durationSlow callsErrorsActivity
Average and p95 latencies; measurements depend on configured API

Endpoint Performance

Click a row to inspect
ApplicationMethodEndpointRequestsAverageP955xx errorsStatus
QuestData DTU▤
—
Azure SQL DTU %
SQL CPU◉
—
CPU utilisation %
Data I/O↗
—
Data I/O utilisation %
Log writes≡
—
Log write utilisation %

QuestData (Azure SQL)

MSSQL

ERP Database / VM

MySQL + Azure VM

Expensive SQL Queries

Requires backend query monitoring endpoint
DatabaseQuery fingerprintExecutionsTotal CPU (ms)Avg duration (ms)Operation

Incident Timeline

Correlation ≠ causation
TimeSystemSeverityIncidentMetricRelated activity
To identify who truly caused expensive database work, instrument API → database query tracing using a request ID. Overlapping timestamps alone do not establish responsibility.
Intended deployment: admin2.questplus.in/monitor. Standalone preview only; for production use the supplied native React route with server-side RBAC. Configuration: Start in demo mode, then enter the monitoring API URLs. This dashboard requests read-only aggregated monitoring endpoints. Do not paste database credentials or admin API secrets into this HTML. Browser requests require HTTPS, CORS permissions and server-side authentication where applicable.

Connection and data mapping guidance

Expected API responses and flexible field mapping

Each endpoint should return JSON. You can enter a response data path such as data or data.items; leave it empty for a root-level response. If your backend uses different property names, provide a JSON mapping object, for example {"userId":"user_id","durationMs":"response_time_ms"}. Left keys are dashboard field names; right values are fields in your response. Mappings apply per record; they support nested property paths.

Configured endpoints are fetched directly from the browser. Authentication should be through existing secure same-origin sessions or an authorised proxy. Cross-origin APIs need CORS configured on the server. Avoid tokens in query strings or browser local storage.

Supported JSON examples
GET /monitor/overview
{"dtu":78,"cpu":54,"dataIo":65,"logWrite":27,"requests":4000,"slowRequests":120,"errors":4,"updatedAt":"2026-11-18T13:00:00Z"}

GET /monitor/users
[{"userId":"U123","name":"Admin A","type":"admin","app":"old-admin","requests":42,"durationMs":126000,"slowCalls":5,"errors":0,"activity":"Content import"}]

GET /monitor/apis
[{"app":"new-admin","method":"POST","route":"/api/questions/import","requests":70,"avgMs":800,"p95Ms":2400,"errors":1}]

GET /monitor/sql-trend
[{"time":"2026-11-18T12:00:00Z","dtu":65}]

GET /monitor/db-health
{"mssql":{"dtu":78,"cpu":54,"dataIo":65,"logWrite":27,"workers":15,"sessions":9},"erp":{"cpu":42,"memory":61,"disk":37,"connections":25,"slowQueries":3}}

GET /monitor/queries
[{"database":"mssql","fingerprint":"SELECT ... FROM ...","executions":500,"cpuMs":12800,"avgMs":45,"operation":"Report generation"}]

GET /monitor/incidents
[{"time":"2026-11-18T13:00:00Z","system":"QuestData","severity":"high","title":"Sustained DTU above 90%","metric":"DTU 94%","activity":"Report export (correlated)"}]
API authentication and deployment notes

For local HTML opened with file://, browser security restrictions may block live API calls. Serve the HTML from your admin site's HTTPS domain. The connection test uses fetch with credentials: same-origin and never stores credentials. Your server must authenticate the user, authorize monitoring access, and only expose aggregated read-only telemetry.