Skip to content

Nicolaas Botes

My feedback

1 result found

  1. 81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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!

    An error occurred while saving the comment
    Nicolaas Botes commented  · 

    That is excellent news Priya! I think this "custom alert" feature should definitely allow one to create the alert based on the output of a T-SQL script, rather than link it to a performance counter object. This allows more flexibility in the sense that you can either query the sys.dm_os_performance_counters or even the underlying replication system tables.

    Nicolaas Botes supported this idea  ·