Splunking ZenDesk Tickets

[marcoscala]

Did anyone tried to import in Splunk info from ZenDesk? I'd like to import infos about ticket status using the ZenDesk Api but it looks not so easy.

Thanks,
Marco

[VictorSM]

Helprace has their own API as well (although it may not be as extensive as Zendesk's at this point) http://support.helprace.com/i162-api-documentation-custom-request-forms

[Damien_Dallimor]

I have never used ZenDesk , but their REST API listing tickets endpoint looks pretty straightforward to me.Returns a nicely formatted JSON document which Splunk will understand for field extraction.Uses Basic Authentication (emailaddress/password). Very simple use case for the REST API Modular Input.

http://developer.zendesk.com/documentation/rest_api/tickets.html#listing-tickets

[Damien_Dallimor]

The REST API Modular Input has a feature whereby you can plugin your own custom response handlers and achieve whatever elaborateness you may require. Such use cases for this might be 1) custom pre-processing of the raw response data for indexing in Splunk 2) dynamically constructing subsequent REST requests 3) persisting state back to Splunk.

[hvandenb]

How can you implement the persistent state for subsequent calls?

[satishsdange]

Can't you use DB connect?

[marcoscala]

Damien,
I've been playing a bit with Zendesk APIs but the bad thing is that if for instance you ask for recent updates ( GET /api/v2/tickets/recent.json) you get a huge JSON with a single root element "tickets" and then all the tickets info hierarchy beneath.

ZenDesk APIs provide means to get info about the specific ticket, but then you need a more elaborate form of scripted input to get info in a more precise way.

Thanks,
Marco