Hey everyone!
I've been working on an open-source project called Argus - SystemSleuth.
The idea started with a problem I've encountered while thinking about application debugging:
When a user reports that something didn't work, a stack trace or API error often tells us where something failed, but not necessarily whag happened across the enire user journey.
For example:
A user selects a PDF, attaches it to an email and taps Send. The upload times out.
A conventional log might tell us that an HTTP request failed. But understanding the sequence of user actions, screen transitions and network events leading up to that failure can be equally important.
I'm exploring whether a structured runtime trace can make this kind of debugging easier.
What Argus currently explores:
● An in-memory, bounded flight recorder for capturing session events.
● Android Activity/Fragment lifecycle and user-interaction tracking.
● Network-event instrumentation through OkHttp.
● Session-level diagnostic analysis using AI providers, with a heuristic fallback.
● A sample Android app that reproduces an attachment-upload timeout and demonstrates the diagnostic flow.
A little context about it's current state:
This is still an early-stage experiment, not a production-ready observability SDK. The expected-workflow-versus-observed-execution comparison is also still a work in progress, rather than a fully integrated Android feature.
Privacy and sensitive-data handling need further work too, so I'd currently treat it as something to experiment with using test data rather than real user sessions.
Github: https://github.com/Deven264/Argus-SystemSleuth
It's liscensed under Apache 2.0.
I'd particularly appreciate feedback from people working on Android, debugging tools, observability or developer infrastructure.
- Do structured user-journey traces provide meaningful value beyond conventional logs and crash reports?
- Which events would you consider essential to capture when diagnosing application failures?
- What privacy safeguards would you expect before using a tool like this in a real application?
I'm sharing this to get honest technical feedback and improve the project. Criticism and suggestions are welcome!
Disclosure: I'm the developer of Argus.