Sheldon Hull

← Redgate Monitor

My feedback

4 results found

  1. Use extended events instead of trace when trace initialized due to alert

    98 votes
    7 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Daniel Rothig responded

    Thanks for the suggestion – we’ll monitor how popular it gets

    An error occurred while saving the comment
    Sheldon Hull commented  · 

    Followup. This is really important to support going forward. The overhead for servers is much lower, so the monitoring can actually be more detailed with less impact to server performance. Reducing the monitoring load while gathering more metrics would be a great gain. Any idea of the roadmap for this?

    An error occurred while saving the comment
    Sheldon Hull commented  · 

    The triggering of a trace should not be at any alert, but instead you should specify in the alert configuration that the high, medium, or low level alert would qualify for a quick trace. For instance, dbcc_integrity check alerts shouldn't trigger a trace, but a long running job at the high level could be set to run the trace.

    This is a big deal, as some competing products build this in, allowing you to not impact server performance to trace except on the most important issues.

    Sheldon Hull shared this idea  · 

  2. Offer integration with power bi

    20 votes
    0 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Sheldon Hull shared this idea  · 

  3. Allow trace to be set at the individual alert level and severity

    6 votes
    0 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Sheldon Hull shared this idea  · 

  4. Analysis parsing of dates and multiple baselines using a text input search

    3 votes
    0 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Sheldon Hull shared this idea  · 

Feedback and Knowledge Base

(thinking…)