Matt Girolami

My feedback

7 results found

  1. 60 votes
    5 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Matt Girolami supported this idea  · 
  2. 32 votes
    1 comment  ·  Suggestions  ·  Admin →
    How important is this to you?
    Matt Girolami supported this idea  · 
  3. 6 votes
    1 comment  ·  Suggestions  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    Matt Girolami commented  · 

    I would like to see this as well.

    In very high transaction volume systems, often we care more about the number of processes being blocked over a time period than we do how long one process is blocking another.

    Matt Girolami supported this idea  · 
  4. 13 votes
    1 comment  ·  Suggestions  ·  Admin →
    How important is this to you?
    Matt Girolami supported this idea  · 
  5. 36 votes
    6 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    An error occurred while saving the comment
    Matt Girolami commented  · 

    Agree with other comments that more configuration options on this alert would be nice. Being able to filter out jobs would be nice, but having a bit more smarts around comparing job runs vs the average time of previous runs at that same time instead of the last 10 times would be nice.

    As an example, we have various archive jobs that run every few hours, however the time they take to complete differs based on user load, so runs outside of our normal business hours take seconds, while runs during high use period may take an hour or more. This difference in expected times causes this alert to be of low value to us

    Matt Girolami supported this idea  · 
  6. 186 votes
    5 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Matt Girolami supported this idea  · 
  7. 23 votes
    2 comments  ·  Suggestions  ·  Admin →
    How important is this to you?
    Matt Girolami supported this idea  · 

Feedback and Knowledge Base