RocketChat / RocketChat/Rocket.Chat
Enhance server statistics collector
Open
Nobody has claimed this yet.
planned
triaged
type: improvement
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
It could be very useful for the dev team to know:
- How many instances of rocket.chat are running
- Amount of edits to messages made
- Amount of Emojis used
- Amount of voice messages
- Amount of mentions
- Amount of inactive users (users who haven't done anything)
- Amount of active but users who haven't posted anything (or more than one message) [configurable]
- Amount of files uploaded in the last 24 hours (or configurable) [configurable]
- Amount of images linked to
- Amount of urls posted
- Video calls started
- Video calls used
- Video calls ignored
- Length of video calls
- Amount of avatars changed
- Amount of joins to rooms following mentions (#600)
- Amount of each /command used
- Amount of status changes (how many of each too)
- Amount of logins
- Amount of password resets
- Amount of failed login attempts
- Count of the different login types, how many oauth and how many of which type
- Amount of starred channels, direct messages, private groups
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points and lists many possible statistics without selecting a scope. Start by determining which metrics are still required and where the existing server statistics collector lives. Done should mean the agreed metrics are collected and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100