On previous generation MAKO20 system, we were able to monitor the HOST machine resources (CPU, MEMORY, FABRIC, DISK) by using NZ_SYSUTIL_HISTORY table provided out of the box.
On new generation of the system (IPS), we can still do it, but the HOST machine is used in a different way - there are serveral processes/containers that are running on this machine, and the previously known HOST is only one of them. But the table only contains the summary information.
Why is it useful?
|Who would benefit from this IDEA?||This is useful for the DBA/Maintenance teams, to check the health of their machine|
How should it work?
We want to be able to additionally monitor the distribution of resources on the HOST - we want to know how much memory is consumed by each process (so, to do a drill-down). Of course, we don't want to get rid of the previous monitoring.
And we need to have that in the DB itself too, so either we need a new table with details by process, or we need to change the format of the current table (but in this case, we want to keep the "overall" information there too, as it is also useful.
|Priority Justification||This is needed as we consider current "overall" way of monitoring not enough to be sure that are system is in a good state.|
|Customer Name||Andrzej Gacek - Volvo|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions