Exceptions : Issue tracking system integration?

[Guest]

Hi, Is there any way of extracting data from "Exceptions" section into the issue tracking system? This would be really useful if we could auto-sync and update issues from within a single system. Is there any API for doing it? Perfectly I'd love to see 2 way integration where developer can close the issue in our internal system and this would get closed on both platforms. Also updating of statistics (affected users, how many time exception have been thrown etc.) in our internal system would be a nice thing - so we can get an overview and schedule items to be fixed in a more efficient way. Regards, Lukasz

[Guest]

Hi Lukasz Unfortunately we do not have an open API for this, though we have had a few requests for interacting with the exceptions data from outside the web client. We are looking into opening up our APIs in the near future and apart from extracting the statistical data and trends, the exceptions data is an obvious candidate especially for integrating with other systems. Our current thinking is a rest-like interface for extracting a well defined subset of the data already available in the web client. As for your described scenario, there are some caveats to extracting e.g. the number of times received and number of affected users as those are very dynamic numbers and changes as data is received from more and more users. We are not interested in providing a "syncing" API but rather an API to query for the immediate status of the a given exception. Moving the dynamic data from our system to your bug tracking database would require more than a one-time export/import but rather a periodic pull and merge job on your side. Is that a valid scenario for you? We have no specific timeframe for the API endpoints at this point, but I would like to get back to you on the specifics of the exception integration into an external bug tracking database at a later point. Hope this helps, at least in terms of clearing up what is available now and further down the road. Regards Soren EQATEC Team

[Guest]

Hi Soren, Polling API would be ok to start with - but ability to set values back (like state + maybe some comments) would be nice as well. We also use a secondary crash reporting system (where user can add his private data to the crash report + description + logs etc.) we currently add common id (GUID) to both eqatec monitor (as part of context field) and our secondary system (as ID). It'd be nice if we could merge both sources in our one issue tracking system. Regards, Lukasz

[Guest]

Hi Lukasz Yes, I should have mentioned that for the exception API you would obviously be allowed to set state, open and close and add comments using some rest-like API, so I think we are on the same page there. With regards to your tracking/common id, what is your thinking on merging from the two systems? How do you ideally see the interactions and the API needs to support your scenario? Regards Soren EQATEC Team