Improved notifications and recovery for target failures

4 コメント

  • Jason Kadlec
    コメントアクション Permalink

    YES!!! How are more people not blowing up this thread??!?!

     

    We have records of failed attempts - where the attempt was sent to a Redis based queue - pretty much the lightest thing our server to do.

    At the time stamp of the "failed attempt" - we have NO record of any downtime, errors or anything close to a maxed out CPU/Memory etc.

     

    WE NEED LOGS!!! 

     

    I would love all the same things Collin has requested, but I would start the list at #3, and put the link and the response platforms at the bottom of the list.

     

    We need, need, need logs so we know why something failed, and logs while it is disabled so we can back-fill manually.

     

    Thanks!

     

    Jason

    1
  • Nathan Stowe
    コメントアクション Permalink

    Just got this error but there are no failures saved under my Channels > API > Target Failures section. :(

    0
  • Michael Southwell
    コメントアクション Permalink

    Completely agree with everything Colin said above! This would be a vital improvement to the current setup. We are currently trying to figure out how to integrate alerts based monitoring for this, but we are having trouble figuring out the best approach, because emails are only being sent to the agents. which can often get missed, meaning it can be hours before the issue is resolved and there is no option to retry any previously failed attempts, short of manually going through all tickets since the outage!

    0
  • Shawn Varughese
    コメントアクション Permalink

    i agree we should be able to turn off the automatic deactivation of extensions

    0

サインインしてコメントを残してください。

Powered by Zendesk