Zendesk connector partly broken

Elastic Search
1

I am posting my issue here, because I could not find the zendesk connector source
on github, Is it close-source? If there is a better place to post it, please inform me.

I added the zendesk connector and the jobs "incremental" and "delete" are working fine,
but the "full" job errors from the beginning.

The full job expects the "X-Rate-Limit" response header,
but i think it is ""X-Rate-Limit-Limit" and/or "x-rate-limit-remaining"

Error after less than 5 seconds
Updated 0 items
Failure caused by: KeyError: key not found: "X-Rate-Limit"

I uploaded the diagnostic bundle here:

2

Hi @Zetanova

I could not find the zendesk connector source
on github, Is it close-source?

It is closed-source, yes. Enterprise Search is making incremental progress in opening select components (including our connectors), but at this time our Zendesk connector is not in a public repo.

The full job expects the "X-Rate-Limit" response header,
but i think it is ""X-Rate-Limit-Limit" and/or "x-rate-limit-remaining"

It's actually getting responses of x-rate-limit instead of X-Rate-Limit. Zendesk has been made aware of this issue - they seem to have changed the casing of their header without notice. We expect our next releases to contain a fix, but in the mean time, I encourage you to raise a support request with Zendesk to request that they restore the original casing of this header.

3

The general convention is to lower http-header and compare.

Meaning that user posted header values are always lowered
and all header in the http-response too.

But off course a case insensitive string compare operator works too.

AWS WAF, MS Exchange rules and multiple other popular services are working like that.

4

@Sean_Story Thanks for your response.

5

@Sean_Story zendesk ticket is open

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.