Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.
The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.
💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.
🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.
Start by sharing what could be better - the community and our teams will help take it from there.
%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.