Kevin Raney
My feedback
2 results found
-
81 votes
Thanks for the votes and comments on this one. We're actively considering adding replication latency monitoring and alerting to Redgate Monitor.
Since this suggestion was raised, we've added a replication page under Estate tab that lists replication agent jobs with their publisher, distributor, subscriber, publication and job status. It doesn't yet show latency or let you alert on it, but it is something we are considering.
Latency is one of several pieces of replication information customers have asked us for and so it woudl be good to know which of these matter to you:
- Publisher to distributor latency (Log Reader agent delivery latency)
- Distributor to subscriber latency (Distribution agent delivery latency)
- Number of undistributed commands waiting to be applied to each subscriber
- The most recent replication error text for an agent
- + Alerts on any of the above
Please add a comment saying which of these you'd use!
Kevin Raney
supported this idea
·
-
44 votes
Kevin Raney
supported this idea
·
An error occurred while saving the comment
I'd like the ability to override the Slack WebHook, Channel and username settings the same way you can set alert settings...
SQL Monitor level (where it is now)
Group level
Host Level
Instance Level
Database Level
Alert Type Level
My use case is I would like to have only production alerts go to my #database-alerts-prod channel
and I'd setup my non-prod group slack settings to post to #database-alerts-non-prod.
Setting things at the alert level would also let me create a channel called #database-alerts-blocking and jsut all the blocking notifications there.
This would add a tremendous amount of notification separation to SQL Monitor, we now only send alerts via slack so this is important for us. I can focus on Prod by turning slack notifications off for non-prod but then I don't see my other instance notifications.