Reader small image

You're reading from  Getting Started with Flurry Analytics

Product typeBook
Published inDec 2013
Reading LevelIntermediate
PublisherPackt
ISBN-139781782177128
Edition1st Edition
Languages
Right arrow
Author (1)
Bhanu Birani
Bhanu Birani
author image
Bhanu Birani

Bhanu Birani has more than 7 years of experience in the software industry. He is passionate about architecting, designing, and developing complicated applications. He specializes in creating web, backend as a service, and mobile products suitable for B2B and B2C context. He has expertise in end to end development to create innovative and engaging applications for mobile devices. After years of programming experience in different programming languages, he started developing applications for iOS devices. He started software development around the same time as his graduation and was really interested in learning about the new technologies emerging in the market. He then joined a game development company. After contributing to the gaming domain, he started working on content-based applications and radio applications. He also contributed to hyperlocal geo-targeting using BLE (iBeacons). Over the years, he has gained experience in all phases of software development as requirement gathering, feasibility analysis, architecture design, coding and debugging, quality improvement, deployment, and maintenance.
Read more about Bhanu Birani

Right arrow

Crash Analytics


Last but not the least, crash analysis can be done by the Errors item in the Technical menu item on the side bar in any application page. It gives you a graphical representation of the total errors over time, average errors per session, a detailed view, and exception log. It makes the life of a technical team very easy by helping track mishaps in the application.

The following are the advantages of Crash Analytics in Flurry:

  • We can prioritize the errors and crashes that have been tracked. We can do this using the same SDK

  • We can receive an e-mail notification of the crash so that the implementers are notified of the application crash before it's too late

  • We can get full stack traces of errors with symbolication

  • We can find errors listed by their name

We will be learning about Crash Analytics in detail in Chapter 4, Technical Analytics.

lock icon
The rest of the page is locked
Previous PageNext Page
You have been reading a chapter from
Getting Started with Flurry Analytics
Published in: Dec 2013Publisher: PacktISBN-13: 9781782177128

Author (1)

author image
Bhanu Birani

Bhanu Birani has more than 7 years of experience in the software industry. He is passionate about architecting, designing, and developing complicated applications. He specializes in creating web, backend as a service, and mobile products suitable for B2B and B2C context. He has expertise in end to end development to create innovative and engaging applications for mobile devices. After years of programming experience in different programming languages, he started developing applications for iOS devices. He started software development around the same time as his graduation and was really interested in learning about the new technologies emerging in the market. He then joined a game development company. After contributing to the gaming domain, he started working on content-based applications and radio applications. He also contributed to hyperlocal geo-targeting using BLE (iBeacons). Over the years, he has gained experience in all phases of software development as requirement gathering, feasibility analysis, architecture design, coding and debugging, quality improvement, deployment, and maintenance.
Read more about Bhanu Birani