This document is out of date.
Please find the new WWWO post for Database Performance Analyzer here!
This document is out of date.
Please find the new WWWO post for Database Performance Analyzer here!
I have two suggestions that would be of tremendous value to our company:
1) Today if there were a question whether Ignite sent an email or a trap, we would have no documentation that would assure what actions were taken. It would be great if, like in SQL Agent, there were a list of actions taken and any errors in taking an action listed. That way we could demonstrate that an email was sent or a trap was generated.
2) If we upgrade a server to a new instance, there is a transition period where we do not wish to monitor the instance but where we may need to reactivate it or we may need to access the history of its monitoring (for a before-and-after comparison). However, the current options for leaving the monitor in place cause problems for our alerting process. If we leave the monitor on, we will generate instance availability alerts that are false. If we turn it off, we have no way of showing that this was done on purpose and monitor-the-monitor processes will see it as a problem and alert falsely. It would be nice if instead of just on and off, there were a third status of "archived" or "decommissioned" to show that the instance is off, but is off on purpose and can safely be ignored by monitor-the-monitor or in the GUI.
Nice ideas augustinius. I've added a feature requests for you.
I created the request for you for this at http://thwack.solarwinds.com/ideas/4058
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.