Improved notifications and recovery for target failures

Nicht geplant

9 Kommentare

  • Jason Kadlec

    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

    6
  • Nathan Stowe

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

    0
  • Michael Southwell

    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!

    2
  • TekDash Support

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

    1
  • Gautam Madaan

    A way for our systems to know the trigger disabled so we can react accordingly. Much needed! We are having to work around this, just so we can improve availability of our system.

    1
  • Robert Sutherland

    This is beyond frustrating. Targets are disabled and we can't even figure out why. And no response is given to remedy the situation.

    0
  • Collin C

    +1, me from 3 years ago. Again had a big issue caused by how Zendesk handles target failures.

    0
  • Wayne Allen

    +1 also experiencing disabled targets, but no evidence of our system receiving any requests.

    1
  • Carl Joseph
    Zendesk Product Manager

    Hey Colin, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.

    We wanted to let you know that we can not accept this feature request due to an upcoming deprecation of external targets in preference for webhooks. We wanted to ensure we closed this loop to remain transparent for you and others to remain up to date on our current plans. 

    At this time we are going to close this post for comment and mark it as “not planned”. If you are interested in learning more about this and other features being built please make sure to check out our Community events, What’s New Community Topic, and Zendesk Updates. Again, we apologize for our delay and appreciate you being a valuable Zendesk Community member

     

    that with the exception of Email Targets, all 

     

    Just circling back on this one to mention that with the exception of Email Targets, all External Targets are being deprecated in preference for webhooks. 

    0

Post ist für Kommentare geschlossen.

Powered by Zendesk