My team has installed 1.1 and we have been using it for around a week now and have a few notes to pass on.
In Instance View if we choose to FILTER by tag, we only see two servers returned when we choose a single tag. For example, we have several servers tagged as Production in our environment, if we open the Tags filter and click the “By Count” radio button, it shows the correct number of Production servers, but when we check the box for the Production tag, only two are returned. Same for other tags.
Ability to delete records from the Instances > Ignored view (We want to get rid of the NA’s (Falsely found servers)). Some might come back, but if not, we’d like to reduce the clutter
Ability in Administration > “Manage Discovery Options” to have a check-box to not discover NA Versions’s maybe also ignore specific editions (don’t discover Express/workstation/Developer etc.)
Administration > “Manage Discovery Options” multiple logins per domain (or ability to have multiple domains with the same name, but different login)
For Version filtering (on any page with that filter (Instances main page, Explorer)) instead of seeing tons of different versions (one for each SP applied), have them all rolled up into a 2000, 2005, 2008, 2008R2, 2012, 2014, etc with a plus box to the left of the name that people could click if they wanted to drill down to specific patch/version
Monitoring Thresholds; we would like to set the threshold for monitoring alerts (health check alerts). 79% of disk full is something we don’t care to see, we would set it for a much higher number. Consider making this a per monitored instance value?
Ability to view and reset dismissed alerts
Thanks for the feedback! It sounds like you’re running into a bug in filtering and I think it may be worth letting Idera Support know about it so they can open a case for tracking. On your enhancements, one by one:
Deleting from ignored list – noted. I’ll see if I can put together a script for this in the meantime.
Manage discovery – If you take a look at the Auto Registration Options, is that what you’d envision (but for discovery)?
Multiple logins – noted, good idea
Version filtering – again, good idea
Monitoring thresholds – makes sense to me
View and reset dismissed alerts – By reset I take it to mean you would allow the issue to be shown as critical, etc immediately upon resetting? Reset individually or reset all, or both?
Thanks for your feedback! The issue you’re seeing sounds like it may be a legitimate product issue. If you would, please contact Idera Support either using the Customer Portal (idera.secure.force.com) or by emailing [email protected] We’ll generate a case we can use to troubleshoot the issue and, if necessary, get some assistance from Development.
Your enhancement requests have been brought to the attention of Product Management, and will be considered for potential inclusion in a future release.
>>Manage discovery â€“ If you take a look at the Auto Registration Options, is that what youâ€™d envision (but for discovery)?Manage discovery â€“ If you take a look at the Auto Registration Options, is that what youâ€™d envision (but for discovery)?
Yes, that but also adding another option to prevent any server with Version NA from being discovered.
>> View and reset dismissed alerts â€“ By reset I take it to mean you would allow the issue to be shown as critical, etc immediately upon resetting? Reset individually or reset all, or both?
By Reset I mean, if someone dismisses an alert, we’d like the ability to allow it to send us alerts again, even if the situation hasn’t resolved. My understanding is that currently, once it has been dismissed, it won’t alert again until the situation that caused it is resolved and the issue then happens again.
Got it, will enter the feature requests into our system! Thanks!
What about making a report or a page on the system that shows all instances that have disabled monitoring or individual databases that have disabled monitoring. I think it’s something we would like to audit from time to time.
Powered by IDERA