Well you can think different, some links below point to a status screen I did for a VisualWorks server application Red varies from 0-100 % and the sum of the other colors Green, Blue, Light Blue, and Purple are measured as state changes as work progressed for 4 different processes. http://smalltalkconsulting.com/clientSupport/L/opsguide/Image18.gif http://smalltalkconsulting.com/clientSupport/L/opsguide/Image17.gif http://smalltalkconsulting.com/clientSupport/L/opsguide/Image16.gif I think... goodness that was 12 years back, I did something like... footaskcounter := footaskcounter + 10. foo msg1 footaskcounter := footaskcounter + 10. foo msg2 footaskcounter := footaskcounter + 10. foo msg3 footaskcounter := footaskcounter - 30. As you can see from the gif files it was easy to look at the visual and understand what the application was *doing*. The support team could look at Image18.gif and fully understand what was happening. Operations only knew that Image18.gif was *normal* and that Image16.gif was the loss of the mainframe network data feed connection,. and for Image17.gif the image was doing nothing useful, idle, but not insane... On 2009-09-28, at 6:24 PM, Schwab,Wilhelm K wrote:
Thanks! I was thinking in terms of "anything but Smalltalk" to avoid the obligatory FUD and Mud slinging. However, it does sound like a useful idea, and if the code is already written, it can't hurt to see what it shows. If it flags something, then I can figure out whether I can get the IT types to believe it.
Bill
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================