The Rocket.Chat plugins talk to the Rocket.Chat REST API. They need a user
that holds the view-statistics permission (the stats API is not public).
rocketchat-stats: total and active users, online users, channels, messages, uploads and file-storage usage.rocketchat-version: installed Rocket.Chat version, EOL check.
Create a dedicated Rocket.Chat user with permission to read statistics. How you grant the permission depends on the edition.
Custom roles are an Enterprise feature. In the admin area (top-left avatar menu > Administration):
- Permissions > New Role: name
stats, scopeUsers, grant only theView Statisticspermission, Save. - Users > New: username
rocket-stats, assign a password manually, add thestatsrole under Roles, Save.
CE does not allow creating custom roles through the UI; you repurpose a built-in role instead.
- Simple: create
rocket-statswith the built-inadminrole. Overprivileged but one step. - Narrower: in Administration > Permissions, tick
View Statisticson the built-inbotrole, then createrocket-statswith thebotrole. Thebotrole also exempts the user from rate limits, which is acceptable for a monitoring account.
The plugins are then called with --url (e.g.
https://rocketchat.example.com/api/v1), --username=rocket-stats and
--password.
Shared across both Rocket.Chat plugins (run <plugin> --help for the full
list):
--url: Rocket.Chat API base URL. Defaulthttp://localhost:3000/api/v1.--username/--password: credentials of the monitoring user.--insecure: skip TLS certificate verification.--no-proxy: ignoreHTTP_PROXY/HTTPS_PROXY.--timeout: network timeout in seconds.
The shipped basket activates both Rocket.Chat plugins through one Service
Set, assigned via the rocketchat tag on the host:
- Rocket.Chat Service Set: runs
rocketchat-statsandrocketchat-versionagainst thestatsuser above.