QACR Crash Reporting System Architecture and Features

Author Jiang Baogui, an Android development engineer at Qunar since 2011, introduces the QACR (Qunar Android Crash Reporting) system, which he helped design and maintain.

The system has grown from a 2‑3 MB client and a team of 5‑7 developers to a 30 MB+ client, a team of over 100, and supports dozens of business lines, evolving from simple crash collection to a real‑time, high‑concurrency processing platform.

Key challenges include handling a large development team, high‑concurrency multi‑business traffic, diverse mobile devices and ROM versions, multi‑channel adaptations, and irregular backend releases, all requiring rapid real‑time exception processing, monitoring, alerting, and quality quantification.

QACR’s architecture consists of a client SDK that encrypts and compresses crash data, which is decrypted and decompressed by Pitcher servers, then sent to a loganalysis server for de‑obfuscation and classification. The data is forwarded via QMQ to business servers that provide CRUD operations on Elasticsearch, authentication, reporting, and crash‑rate calculations.

The front‑end includes dashboards for crash trends, version/device distribution pie charts, overview panels, and per‑business crash trends, as well as detailed bug lists, reports, and user interaction trace views.

Recent update plans focus on increasing crash trend visibility, automatic bug‑to‑git linking, crash screenshot capture, release event timelines, visual alert/report configuration, bug detail enhancements, and support for uploading mapping/symbol files.

A “5‑minute quick integration” guide is provided, along with links to documentation, backend address, and contact persons for Android SDK, iOS SDK, backend services, and overall design.