Registered rules
missing_composite_index
Missing Composite Index
- Category
- index
- Severity
- high
- Engines
- All live engines
- Default fix zone
- auto_pr_safe
full_table_scan
Full Table Scan
- Category
- query_shape
- Severity
- high
- Engines
- All live engines
- Default fix zone
- suggest_only
filesort_or_temp_table
Filesort or Temporary Table
- Category
- query_shape
- Severity
- high
- Engines
- All live engines
- Default fix zone
- auto_pr_safe
select_star
SELECT * on Wide or BLOB Table
- Category
- query_shape
- Severity
- medium
- Engines
- All live engines
- Default fix zone
- auto_pr_safe
unbounded_pagination
Unbounded Pagination
- Category
- query_shape
- Severity
- high
- Engines
- All live engines
- Default fix zone
- auto_pr_safe
high_rows_examined_ratio
High Rows Examined Ratio
- Category
- query_shape
- Severity
- medium
- Engines
- All live engines
- Default fix zone
- suggest_only
n_plus_1_query_loop
N+1 Query Loop
- Category
- orm
- Severity
- high
- Engines
- All live engines
- Default fix zone
- suggest_only
resource_pressure_victim
Resource-Pressure Victim
- Category
- configuration
- Severity
- medium
- Engines
- All live engines
- Default fix zone
- suggest_only
Server configuration rules
These read the server itself rather than a query, and they run on a schedule against a pair of scans. That is what lets them do something a query rule cannot: report that a condition has been resolved. A finding opens when a rule fires, closes when the same rule reports healthy, and reopens as a new episode if the condition returns. Severity is computed per evaluation, so it is not listed here.
bounded_buffer_pressure
A bounded buffer is undersized
- Engines
- mysql, mariadb
- Evidence
- observational
- Fix
- Can be applied automatically
- Scope
- instance
buffer_cache_pressure
Buffer cache pressure
- Engines
- postgres, mysql, mariadb
- Evidence
- observational
- Fix
- Can be applied automatically
- Scope
- instance
categorical_setting_off
Setting is off
- Engines
- postgres, mysql, mariadb
- Evidence
- exact
- Fix
- Can be applied automatically
- Scope
- instance
connection_saturation
Connections filling up
- Engines
- postgres, mysql, mariadb
- Evidence
- exact
- Fix
- Reported only
- Scope
- instance
dead_tuples_accumulating
Dead rows accumulating
- Engines
- postgres
- Evidence
- observational
- Fix
- Reported only
- Scope
- connection
disk_fill_trajectory
Disk filling up
- Engines
- postgres, mysql, mariadb
- Evidence
- derived
- Fix
- Reported only
- Scope
- instance
host_swap_activity
Host is swapping
- Engines
- postgres, mysql, mariadb
- Evidence
- observational
- Fix
- Reported only
- Scope
- instance
low_cardinality_index
Low-selectivity index
- Engines
- mysql, mariadb
- Evidence
- observational
- Fix
- Reported only
- Scope
- connection
memory_overcommit_risk
Memory overcommit risk
- Engines
- postgres, mysql, mariadb
- Evidence
- derived
- Fix
- Reported only
- Scope
- instance
myisam_high_write_workload
MyISAM table-lock contention
- Engines
- mysql, mariadb
- Evidence
- exact
- Fix
- Reported only
- Scope
- connection
myisam_no_key_buffer_tuning
MyISAM key buffer undersized
- Engines
- mysql, mariadb
- Evidence
- exact
- Fix
- Needs your approval
- Scope
- instance
postgres_pending_restart
Change pending a restart
- Engines
- postgres
- Evidence
- exact
- Fix
- Can be applied automatically
- Scope
- instance
purge_lag
Purge is falling behind
- Engines
- mysql, mariadb
- Evidence
- observational
- Fix
- Reported only
- Scope
- instance
replication_lag
Replication lag
- Engines
- postgres, mysql, mariadb
- Evidence
- observational
- Fix
- Reported only
- Scope
- instance
stale_statistics
Statistics are stale
- Engines
- postgres, mysql, mariadb
- Evidence
- exact
- Fix
- Can be applied automatically
- Scope
- connection
vacuum_horizon_blocked
Cleanup is blocked
- Engines
- postgres, mysql, mariadb
- Evidence
- observational
- Fix
- Reported only
- Scope
- instance
wraparound_risk
Transaction-ID wraparound
- Engines
- postgres
- Evidence
- observational
- Fix
- Reported only
- Scope
- cluster
How rules run
Deterministic rules run before AI analysis. A query rule applies only to its declared engines and emits evidence, an affected scope, a confidence level, and a proposed-fix hint. Both registries above are rendered from the same canonical registrations the analysis workers use, so neither list can drift from what actually runs.