Suggestions
Welcome to the Redgate Monitor feature suggestions list. Tell us how we can improve Redgate Monitor by voting on these suggestions or by submitting your own ideas.
This is the easiest way to make an impact on Redgate Monitor’s roadmap. Check out the completed suggestions to see how your ideas have influenced us in the past. Please note that this list is one of multiple sources that drive our development, meaning that we will not always implement the highest-ranking suggestions.
To give your idea the greatest possible impact, please follow these guidelines:
- Describe the goal you’re trying to accomplish, rather than a specific solution to get there
- If you have a favoured solution, add it as a comment to your suggestion
- Give us as much context as possible
- Only make one suggestion per post. If you have multiple ideas, submit them in separate posts
- Comment and vote on existing posts to develop the ideas — the Redgate Monitor team will often stay quiet initially about new suggestions to see what you have to say!
If you have any questions visit the Redgate Monitor forum.
43 results found
-
The ability to publish custom metrics and alerts to your website for review and easy addition to community driven submissions. I have tested
The ability to publish custom metrics and alerts to your website for review and easy addition to community driven submissions. I have tested on my own systems and would like to quickly post up the custom metric and alerts I have created instead of current process.
1 voteCurrently we use an email submission system – our sumission volume is still too low to implement an automated process
-
SQL Server agent job alert
Say somehow the sql server monitor wasn't enabled and some job failed on one of the monitored servers that time; when the SQL Server monitor comes back online I would appreciate, it showing this error, in the same manner, the monitor tool shows the overdue alerts for Integrity check, backups etc
1 voteWe decided against this in order to avoid a scenario where users are greeted by an onslaught of Job Failure alerts when they add a new monitored server
-
why It splits the server and port
when I try to add the sql instance to monitor , I have to use port and when I do so it splits into two servers. also host and instance is bit confusing , why it goes as local for anyserver you addd to monitor
0 votes
- Don't see your idea?