You can already within the software disable the scrolling, that way the list of entries isn't jumping around. (setup-general-interface settings) Not having the "line" is something you can do already too, but giving the "line" the same color for all statusses. (same screen as above)
I do like the idea of % completed; I'll have a look at how this can be done. Having all those columns (or option for it), is not that simple to add/implement. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom Sent: Wednesday, March 28, 2007 8:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] GUI make-over - more items Hi Dirk, "Add status column" - oops. Not in front of the software. Didn't recall that. "TURN OFF update": Again, we use our custom outputs (web pages, etc) to check the status of items. The only time we look at the GUI is to add/modify checks. The colors are distracting. The moving cursor as checks are being performed only makes sense when the list is sorted a certain way... So how about an option to just turn that feature off (vs changing all colors to be the same). Check results would still be displayed in a column. So would round trip results... Maybe a batch update of the display after all checks made instead of item by item. "Ability to add columns:" -- This is the big ticket request. Why other fields? Again - we use the interface to update/edit checks. We constantly have lots of changes - and we frequently changing our escalation/response process. So, for example, I want to see what checks are PING checks. It would be nice to be able to sort based on check type to group the PING checks together while I make changes/confirm config. Do any of my database checks have second knock turned on? It's all around being able to look at the current check config in different ways - and using the GUI as a filtering tool. I would like to see pretty much anything that has a 1-to-1 relationship with the check: Depends on (as a column, not a tree) Check type Invert Status Flag Second Knock Timeout Number of alerts defined Number of outputs - useful to see if you "missed anything in the setup" RRD Roundtrip logging RRD UpDown Logging RRD Checkresult Logging Log to Syslog Server Flag syslog facility syslog message (maybe not this one......) Ignore priority when down flag When to check (priority) Start Cycle - so I group all my disk space checks together, then compare the start cycles to make sure I have them evenly distributed..... "Add Route" flag checked Connect Via setting Keep connection active flag ANOTHER IDEA: Add "Percent complete" indicator for check status when a cycle is in progress up top by the "traffic light". Simply take the (total number of checks configured) / (number performed this cycle + number skipped this cycle). I know it would result in a "jumpy" indicator as one check could cause several to be skipped immediately - but our cycle processing time is 3 minutes, so a visual indicator of location within the check list would be nice. -Tom -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Wednesday, March 28, 2007 11:26 AM To: Servers Alive Discussion List Subject: RE: [SA-list] GUI make-over - more items "Add STATUS column instead of colored lines to make it easier to sort based on current status." => this is already in Servers Alive "Ability to TURN OFF the update of the GUI and just use it to manage checks. " => meaning that it does not show the status nor the roundtrip nor the response not the colored bar? That seems kind of difficult to combine this with the request about the status column, or am I missing something? "Ability to add more columns to display (check type, second knock, etc) and sort/filter on any column." => you can sort on each column that is in the interface already. What could be the use of the other fiels? Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Vogl, Tom Sent: Wednesday, March 28, 2007 4:46 PM To: Servers Alive Discussion List Subject: [SA-list] GUI make-over - more items GUI Change requests: FIND feature - to find based on Server name, pretty name, or check type, alerts, etc. Ability to add more columns to display (check type, second knock, etc) and sort/filter on any column. Ability to TURN OFF the update of the GUI and just use it to manage checks. Add STATUS column instead of colored lines to make it easier to sort based on current status. -tom -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Monday, March 26, 2007 5:01 AM To: Servers Alive Discussion List Subject: RE: [SA-list] GUI make-over 1. The GUI IS the service or IS the app, so it's interacting directly. If you run the service as system account with desktop interaction and call the gui via the system-tray icon then you're working directly on the service. 2. That's not a gui change that's a totally new feature 3. That's not a gui change that's a totally new feature 4. That's not a gui change that's a totally new feature Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Steve Davis Sent: Monday, March 26, 2007 10:26 AM To: Servers Alive Discussion List Subject: RE: [SA-list] GUI make-over 1) My biggest bugbear with the GUI is the fact you can't interact directly with the service. If running as a service I'd like to be able to go in and make changes but I have to stop the service, fire it up as an APP, make changes, shut down app, restart service. 2) Make if fully manageable via a web interface, including full functionality. See the web interface for IPMonitor for a nice interface. 3) It needs to be easier to make global changes. This has been partially addressed but can go a bit further. I would suggest keeping a separate credentials manager and then you pick the credentials to use in each check. That way when the details change or a password expires you only have to change it once. 4) Network discovery. Provide an option in the GUI to scan a network/subnet and come back with everything it finds, you can then decide what to add into your monitoring. Steve -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: 24 March 2007 17:51 To: Servers Alive Discussion List Subject: [SA-list] GUI make-over Servers Alive exists since some time :-) The GUI didn't change a lot since day 1. We think it's time for some change. The change should be "just" a GUI change not adding features/functionality. If you have some good ideas or have some examples that we could use (as idea), well then just send them over :-) Dirk Bulinckx. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. ______________________________________________________________________ This inbound email has been scanned by the MessageLabs Email Security System on behalf of Electronic Media Ltd. ______________________________________________________________________ To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
