Skip to content

Add documentation for three new database metrics graphs#11604

Open
ekremsekerci wants to merge 1 commit into
mendix:developmentfrom
ekremsekerci:db_bloat_metrics_graphs
Open

Add documentation for three new database metrics graphs#11604
ekremsekerci wants to merge 1 commit into
mendix:developmentfrom
ekremsekerci:db_bloat_metrics_graphs

Conversation

@ekremsekerci

Copy link
Copy Markdown
Contributor

Summary

Adds documentation for the three new database graphs. All three appear on the Metrics page under Database Statistics, ordered to match the frontend's graph config:

  • Average Database Bloat Ratio — percentage of dead rows across all user tables in the database (mxdatabase_avg_bloat_ratio).
  • Maximum Table Bloat Ratio — bloat percentage of the single most bloated table, split into two series so Mendix system tables and application tables are diagnosed
    independently (mxdatabase_max_table_bloat_ratio).
  • Largest Table Size — size in bytes of the single largest table, with a per-point tooltip carrying the table name (mxdatabase_largest_table_size).

Changes

  • content/en/docs/deployment/mendix-cloud-deploy/metrics.md — three new subsections in the Database Statistics section, after Migration to gp3 Storage Instances.
  • static/attachments/deployment/mendix-cloud-deploy/metrics/db-avg-bloat-ratio.png
  • static/attachments/deployment/mendix-cloud-deploy/metrics/db-max-table-bloat-ratio.png
  • static/attachments/deployment/mendix-cloud-deploy/metrics/db-largest-table-size.png

Anchors

The following anchors are referenced by the frontend's graph config:

  • #Trends-dbmxdatabaseavgbloatratio
  • #Trends-dbmxdatabasemaxtablebloatratio
  • #Trends-dbmxdatabaselargesttablesize

@OlufunkeMoronfolu OlufunkeMoronfolu self-assigned this Jul 24, 2026
@ekremsekerci
ekremsekerci force-pushed the db_bloat_metrics_graphs branch from 134896e to 75d366c Compare July 24, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants