Hello,
We're an MSP and we're very pleased with the SQL Sentry monitoring platform. We have multiple customers with monitored targets, most of them being IaaS installations of SQL Server (VM / on-prem).
With time, we've built a hefty collection of Advisory Conditions that we're using as part of our managed solution. But, all of these Advisory Conditions are SQL Server condition types.
Recently, we got new customers that use AWS RDS SQL Servers, and customers with Azure SQL Database targets.
And now we're facing a problem:
What will we do with all of our Advisory Conditions?
They wouldn't work for the new AWS RDS and Azure SQL DB targets.
That means that now we have to duplicate all of our Advisory Conditions for RDS and Azure SQL DB.
And what if we get new customers in the future with Azure DW targets? Then we have to do it all over again for all advisory conditions.
Shouldn't there be a more "flexible" solution that would allow us to maintain a single Advisory Condition that could work on all SQL Server target types?
I understand the current limitations due to how the conditions and interface are implemented, due to how different target types have different performance counters, different version numbers, and so on.
I'm thinking, as a feature request, perhaps there should be a more "flexible" interface when editing a SQL Server advisory condition, in order to allow the same condition to apply to the different SQL Server target types.
For example, have different "tabs" for the same condition with configurations specific to each target type.
I wouldn't even mind having to manually specify the condition rules per each of the target types (although an easy "copy to" functionality could definitely be helpful). As long as it's under the "umbrella" of the same Advisory Condition.
What bothers me the most is having to actually maintain separate condition objects per each target type... Which means that:
- It's more work having to create and update these advisory conditions.
- I need to give them different names.
- I need to maintain their Actions separately.
- If I want to disable/override certain Actions for certain groups or sites, I have to do it separately per each target type.
All of this becomes extremely troublesome the more conditions and targets that I have to maintain.
Do you think it's something that the product team could consider for future versions?
Regards,
Eitan
