MaxScale Global Memory Use Indicator

Some of our customers are frustrated by the inability to monitor global memory usage from MaxScale using any internal reporting such as status variables.

Occasionally MaxScale uses a larger than expected amount of memory, be it because large transactions are in-flight or because the history of commands gets unexpectedly large, for example, or due to memory leaks in a current version of a MaxScale service or supporting tool such as SQLite.

The desire is to have a global variable in MaxScale reporting on the current cumulative memory use off all MaxScale services, including the SQLite footprint, so that automated monitoring could become aware of potential problem situations and address them proactively.