CircuitSQL DevSecOps console
circuitsql_monitor@127.0.0.1:5432 · SSL required Synthetic demo data Snapshot 27 Oct 2026, 16:10 UTC

Stage 8 of 9 Monitor Live triageFAIL

10 raw alerts folded into 6 findings

What is broken right now, where, and what happens next? Provenance names the production source behind every number.

Health scoreFAIL
62/100
100 - 5×7 fail - 1×3 warn = 62/100 · target ≥ 85
-17 vs prior 15 min
7 fail · 3 warn · 16 pass
Metrics breachedFAIL
10of 26
limit 0 · 3 warnings
3 bars max 2×
Performance findingsFAIL
6
10 raw alerts · 4 fail / 2 warn findings
from 7 fail + 3 warn
Runtime controlsPASS
7/7
CIS PostgreSQL 17 · H16-H18 verified
verified 27 Oct 2026, 16:10 UTC

Findings

Anti-Alert-Fatigue Correlation: 10 raw alerts (7 fail + 3 warn) → 6 findings · Most severe first, then newest.

Performance findings grouped by root cause with severity, evidence, value, owner, and age
StatusFindingEvidenceValue / limitRouted toOpen for
PASSAll 7 runtime CIS controls pass on the live cluster

The proposed migration in 5 Secure still fails S01, S03, and S06. The gate blocks it before it changes cluster state.

Runtime CIS PostgreSQL 17 controls on the live cluster
ControlCISExpected stateCatalog sourceStatus
CSQL-S01CIS 4.5No PUBLIC grants on orders, customers, schema publicpg_class.relaclPASS
CSQL-S02CIS 4.2SECURITY DEFINER functions pin search_pathpg_proc.proconfigPASS
CSQL-S03CIS 4.3App roles lack SUPERUSER and CREATEROLEpg_rolesPASS
CSQL-S04CIS 4.4Row-level security on every tenant tablepg_class.relrowsecurityPASS
CSQL-S05CIS 5.1No plaintext credentials in SQL or configAST + GitleaksPASS
CSQL-S06CIS 3.1pgaudit logs DDL and role changespg_settingsPASS
CSQL-S07CIS 6.2 / 5.2SSL on, SCRAM-SHA-256 passwordspg_hba_file_rulesPASS

Top SQL Offenders

Open any row for the full SQL, EXPLAIN plan, and index fix.

Top SQL offenders with calls, buffers per call, regression, and share of offender I/O
QuerySourceCallsBuffers / callvs. priorShare of offender I/O

Breached metrics over time

Last 15 min · dashed line is the limit · ratio and delta sit beside each chart.

Idle in transaction, longest

CSQL-M02 · H2 · pg_stat_activity · s · limit 30 s

312.0 s

312 s now · 10.4x limit · bar max 2×

Active sessions

CSQL-M01 · H4 · pg_stat_activity state=active · sessions · limit 1.5 × 8 cores

42.0 sessions

42 sessions now · 3.5x limit · bar max 2×

Top query share of DB time

CSQL-M19 · H8 · pg_stat_statements total_exec_time % · % · limit 20%

41.0 %

41 % now · 2.05x limit · bar max 2×

PostgreSQL Metrics That Matter · All PostgreSQL metrics (26)

M01-M25 plus M06Q across five tabs; 18 probes and the environment audit sit beside them. Fail and warn rows sort first; open any row for triage.

4 BREACHED

Health Overview

Is the database in distress right now?12 metrics4 FAIL1 WARN7 PASS
Health Overview metric table with value, ratio, limit, trend, status, and provenance
Metric · sourceValuevs. limitLimit15 min trendStatusData

Database Subsystem Internals

Is PostgreSQL itself under pressure?7 metrics1 FAIL2 WARN4 PASS
Database Subsystem Internals metric table with value, ratio, limit, trend, status, and provenance
Metric · sourceValuevs. limitLimit15 min trendStatusData

Query Performance Analysis

Which statements cause the load?7 metrics2 FAIL5 PASS
Query Performance Analysis metric table with value, ratio, limit, trend, status, and provenance
Metric · sourceValuevs. limitLimit15 min trendStatusData

Health Probes H1-H18

Are catalog, schema, and runtime invariants healthy across all 18 probes?18 probes2 FAIL7 WARN9 PASS
All 18 PostgreSQL runtime and catalog health probes
Probe · checkCatalog sourceMeasuredThresholdRouted toStatusData

Server & Database Environment Settings

Are PostgreSQL GUC parameters, memory allocation, and host OS settings tuned so optimal SQL can run at peak speed?10 settings3 FAIL5 WARN2 PASS
PostgreSQL server, hardware, operating system, and pg_settings environment audit
Setting · parameterSource / host contextCurrent settingRecommended baselineRouted toStatusData

Runtime containment

Build a supervised quarantine runbook. Dry-run by default; executing it needs two human approvers and never runs from the browser.

Audit Evidence & Raw Output

Audit evidence summary

Live PostgreSQL telemetry, health probes, and statement offender evidence captured for the Stage 8 Monitor triage gate.

Stage
Monitor — Live Triage & Containment
Gate status
BREACHED (4 breached of 7 probes)
Environment
cloudrun-showcase (synthetic-demo)
Health probes evaluated
7 probes (H1–H18 subsystem checks)
Statement offenders ranked
2 top SQL query fingerprint(s) from pg_stat_statements
Telemetry sources
pg_stat_statements, pg_stat_io, pg_stat_wal, pg_stat_bgwriter, pg_settings