RocketChat / RocketChat/Rocket.Chat

[IMPROVE] Hourly rocketchat_users metrics refresh rate

Open
#24,433 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

The Prometheus metrics for rocketchat_users_* (rocketchat_users_active, rocketchat_users_active, rocketchat_users_away, rocketchat_users_non_active, rocketchat_users_offline, rocketchat_users_online and rocketchat_users_total) seem to be refreshed only once per hour. This may also be the case for the data displayed in the rocketchat administration panel.

Steps to reproduce:

Setup a Prometheus monitoring instance with Rocketchat

Expected behavior:

Other metrics, such as rocketchat_ddp_connected_users have a much faster refresh rate, which can be very useful. I would expect rocketchat_users_* to be refreshed in a similar way.

Actual behavior:

rocketchat_users_* is refreshed once per hour.

Server Setup Information:
  • Version of Rocket.Chat Server: 4.4.0
  • Operating System: Docker setup using the official rocketchat image
  • Deployment Method: Docker (Openshift)
  • Number of Running Instances: Tested on three different instances

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the codebase for the rocketchat_users_* Prometheus metrics and compare their refresh path with rocketchat_ddp_connected_users. Verify whether the administration panel uses the same data, then confirm that the user metrics refresh faster than once per hour and add or update coverage for the new behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
prometheus, typescript
Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.