Feature Request: Detect Oversized Tables and Runaway Logs

[drupaladmin]

Feature Request: Detect Oversized Tables and Runaway Logs

Problem

In shared-hosting environments, some databases accumulate outdated tables or runaway logs that keep growing even though the live application no longer depends on them.

This can create unnecessary database size growth and eventually lead to MySQL memory pressure and server instability.

Today, operators often handle this manually:

1. alerts fire on high load
2. scripts identify large tables or databases
3. engineering reviews them manually
4. the operator contacts the customer and helps with cleanup if needed

Request

Add a feature that helps operators detect oversized or suspicious tables earlier and identify likely cleanup candidates.

Desired behavior

• Flag unusually large tables relative to the rest of the database
• Flag fast-growing tables that may indicate log accumulation or stale data growth
• Highlight common bloat patterns such as scheduler or action-log tables
• Show which databases or tables deserve review first
• Provide simple guidance such as:
  • review this table
  • confirm whether the application still uses it
  • consider cleanup if it is obsolete

Important scope

This request is about:

• detection
• prioritization
• explanation
• operator guidance

It is not about:

• automatic deletion
• automatic schema cleanup
• customer-facing actions without operator review

User story

As a hosting operator, I want Releem to flag oversized or suspicious tables early, so I can investigate likely cleanup issues before they create database pressure or destabilize the server.

Success criteria

• Releem identifies suspiciously large or fast-growing tables
• Operators can quickly see which tables deserve investigation first
• The output is useful enough to reduce manual triage work
• The feature provides value even when broader optimization features are still used conservatively