Bump on #6 as well. -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of Barry George Sent: Monday, March 05, 2012 11:01 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Next version
Complete agree with Brett's #6 request - I'd like to add that the configuration front end be webinized for total remote access completely disposing of the client/server engine if possible (or at least augment it). Cheers Barry -----Original Message----- From: Hanson, Brett [mailto:[email protected]] Sent: March-05-12 10:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Next version I'd like to see the following: 1. The ability to increase frequency of checking on checks that have reported down (or checks dependent upon the one that reported down). 2. The ability to specify the frequency of checking on specific checks. For instance, I have an Oracle database that is crashing periodically. Just prior to the crash, the number of connected users takes a large jump. I'd like to start polling the database at a greater frequency and run some tests on the application responsible to gather additional data once the number of connections begins its jump. 3. When I monitor disk space and provide the results to RRDTool, I'd like to reduce the number of times per day I check the disk space. I have tried setting it to 1 in 100 checks, but you then get gaps in the data reported in RRDTool and can't make a meaningful graph from it. 4. Database configured checks. It is cumbersome to make changes to many checks with the current user interface. I'd really appreciate a way to make changes via SQL. I know you've heard this many times before, but this is definitely high on my list. 5. As an alternative to #4, templates for checks could be handy. Most checks are very similar, with only the host or credentials changed. If I could modify the template and the change applies to all 100+ entries based on the template that could save many hours of configuration. 6. Complete separation of the checking engine and the configuration user interface. I see that there should be two processes for Servers Alive, one that performs the checks, and one that interacts with the user. The one that interacts with the user would not necessarily need to run all the time. The checking engine should have no user interface and should run as a service. Due to the way our environment is setup right now, Servers Alive runs simply as a process on a server. We have to be very careful to remember to RDP in to the console to prevent multiple instances of Servers Alive running on the machine at the same time. Thanks, Brett Hanson Systems Analyst Agrium Inc. -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of Dirk Bulinckx Sent: Monday, March 05, 2012 7:16 AM To: Servers Alive Discussion List Subject: [SA-list] Next version I would like to get some feedback on what you would like to see in the next (major)version of Servers Alive...so be creative and let me/us know .... Dirk Bulinckx. Network Monitoring by Servers Alive - http://www.woodstone.nu DNS Hosting with ipv4 and ipv6 on http://www.stellardns.com To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. IMPORTANT NOTICE ! This E-Mail transmission and any accompanying attachments may contain confidential information intended only for the use of the individual or entity named above. Any dissemination, distribution, copying or action taken in reliance on the contents of this E-Mail by anyone other than the intended recipient is strictly prohibited and is not intended to, in anyway, waive privilege or confidentiality. If you have received this E-Mail in error please immediately delete it and notify sender at the above E-Mail address. Agrium uses state of the art anti-virus technology on all incoming and outgoing E-Mail. We encourage and promote the use of safe E-Mail management practices and recommend you check this, and all other E-Mail and attachments you receive for the presence of viruses. The sender and Agrium accept no liability for any damage caused by a virus or otherwise by the transmittal of this E-Mail. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
