You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
mattab
added
the
Enhancement
For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
label
Mar 27, 2015
See matomo-org/matomo-sdk-android#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:
The text was updated successfully, but these errors were encountered: