We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
%GSIZE display on the terminal is not friendly, there are pages you have to go through to find what you are looking for. Running the following from SQL CALL %SYS.GlobalQuery_Size works but you have to be in SQL to see that data. Having it more available to the user would be helpful.
If implementing this I would also recommend adding an alerting mechanism around global growth over time with thresholds that can be set.
This way, if a global is, for some reason, seeing far greater than expected growth, this can be alerted upon before numerous journal files are generated and/or database expansions are caused.
Customers run into this regularly.
We have also had some bugs where ISC's code has caused this behavior.
%GSIZE display on the terminal is not friendly, there are pages you have to go through to find what you are looking for. Running the following from SQL CALL %SYS.GlobalQuery_Size works but you have to be in SQL to see that data. Having it more available to the user would be helpful.
Sylvain, thank you for your idea.
There is a comment on your idea. Please answer it to help your idea to be promoted
If implementing this I would also recommend adding an alerting mechanism around global growth over time with thresholds that can be set.
This way, if a global is, for some reason, seeing far greater than expected growth, this can be alerted upon before numerous journal files are generated and/or database expansions are caused.
Customers run into this regularly.
We have also had some bugs where ISC's code has caused this behavior.