Events Connector for Amazon EventBridge FAQs

Pinned

4 Comments

  • Graham Robson
    Comment actions Permalink

    Is there any way to profile/filter which events to stream, or do you get all events and you have to filter what your interested in?

    With Zendesk Targets your able to do this.

    0
  • David Hall
    Comment actions Permalink

    Hi Graham,

    Thanks for the question.

    At the moment there's only one set of events available (Support Tickets), however as we add events for additional products and objects we intend provide the option to choose which sets of events you'd like to receive.

    Additional filtering can be done using rules in Amazon EventBridge, which will allow you to determine whether a specific event gets directed to the AWS service(s) of your choice, or ignored.

    0
  • Graham Robson
    Comment actions Permalink

    Thanks David,

    I think by events sets you mean, a set per Zendesk products, so the only way now and in the future is to use filtering on the Amazon EventBridge. This means a lot more processing externally, than is currently offered by the combination of triggers and targets, where the filtering is done on the Zendesk side.

    Are their any plans to phase out Zendesk Targets or is Amazon EventBridge another method?

    We'd see some challenges with information security concerns if you can't design and implement at source.

    What's the architecture for handling outages of the Amazon EventBridge, will the Zendesk Events Connector work in a similar way to Zendesk Triggers and disconnect after a certain threshold?

    Thanks Graham

     

    0
  • David Hall
    Comment actions Permalink

    Hi Graham, thanks for the additional input.

    We intend that Triggers/Targets and our Events Connector will co-exist, as Targets service a broad range of external systems.

    Re outages:

    • If EventBridge has a problem delivering events from the Zendesk partner event source to your event bus, it will keep retrying for 24 hours.

    • We store events at the Zendesk end for a period of 7 days, so in the event of a major problem our recovery process would involve "setting the clock back" to roll out those delayed events.  As we add new kinds of events this policy may need to become more nuanced.

    • In the case that the connection between your Zendesk partner event source and your AWS event bus is deactivated, AWS will delete your event bus after 14 days.

    I am keen to hear more about your use case and the challenges you have in mind around event filtering.  I will create a ticket so we can discuss in more detail.

    0

Please sign in to leave a comment.

Powered by Zendesk