DAEMON_START metric should not be greater than APP_READY
- Dominant language
- JavaScript
- Stars
- 6.6k
- Forks
- 903
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 5
Description
**Describe the bug**
Our countly latency dashboard shows DAEMON_START count as greater than APP_READY. This should not be the case, ever. If anything, DAEMON_START count should be lower than APP_READY count, because of users who are running the desktop app with a daemon already running.
**To Reproduce**
No specific reproduction steps yet, need to investigate.
**Expected behavior**
* DAEMON_START count should be less than APP_READY count, always.
* DAEMON_START duration should be less than, or equal to, APP_READY duration, for individual sessions.
**Screenshots**

**Additional context**
Countly metrics dashboard is only available internally at Protocol Labs on the GUI team.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.