@d4rken opened this Issue on March 26th 2015 Member

See https://github.com/piwik/piwik-sdk-android/pull/33

Piwiks Android SDK supports automatic catching and tracking of Exceptions. I raised concerns that Piwik is not really suitable for this to due to lack over server-side tools.

What confused me intially was not understanding the usecase for this functionality. I thought it was a move to offer Piwik as Issue-Tracker/Bug-Tracker (like ACRA or Crashlytics) and i think Piwik isn't suitable for that.
Later i came to the conclusion that i probably missinterpreted it, and the real usecase for this is tracking page flows more accurately.
i.e. tracking this flow:
Entry->PageA->EventB->PageC->EventD->Exception
You could see this as a page flow ending in a crash causing you to do further investigation or being able to use this information in conjunction with a real crashtracker.

Suggestions for improvements:

  • Create an extra category like "Downloads", i.e. "Errors" and use that to move the data out of the "Events" section.
  • Add an option to this new "Errors" section that shows you page flows ending with errors.
  • Add filters for errors by software version and device characteristic.
@mattab commented on March 27th 2015 Member

Hi @d4rken thanks for posting this issue and your detailed thoughts (in https://github.com/piwik/piwik-sdk-android/pull/33#issuecomment-86224096)!

FYI: for now we can't make good progress in this area but having a great Exception/Errors reporting tool is in the scope of what the Piwik platform could offer in the future. we may come back to it in a few months, in relation to #5257 - our first small step towards this greater goal will be #7131

Powered by GitHub Issue Mirror