[Feature]: Count servers that do not run monitor in LinuxGSM Stats
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bash, shell
- Domain
- analytics, cli, documentation
Research direction
Start by reading info_stats.sh and its call sites in command_monitor.sh (lines 319 and 466), then trace the install opt-in and start flows. Done means opted-in installs report after opting in and after starting, without CPU or RAM values, while the once-a-day limit prevents duplicate reports; update the docs to name the commands that send reports.
Written by the indexing model from the issue text.
Description
Priority
priority: medium
User story
As an admin who opted in to stats but only uses start and stop (a one-off server, an occasional game night, or a LAN or online event), I want that server counted, so that the usage page shows every opted-in install, not only the ones running monitor.
Game
No response
Linux distro
No response
Command
command: install, command: start, command: monitor
Problem statement
info_stats.sh is only called from monitor (command_monitor.sh lines 319 and 466). Admins who run a server once or now and then without a monitor cron job never send a report: one-off servers, occasional game nights, LAN parties and other online or offline events. They are missing from https://linuxgsm.com/data/usage/, so the page only counts servers that run monitor.
Scope and impact
scope: all servers
Further information
Also send the daily report from:
install, right after the user opts in to stats.start, after the server has started.
Both should leave out CPU and RAM use: there is none after install, and right after start the values say little.
Since #5198 a report goes out at most once a day per instance, so servers that run monitor send nothing extra. On a day when install or start sends first, the report has no usage values, and monitor sends them from the next day.
GameServerManagers/LinuxGSM-Docs#154 says reports are sent "when stats run". The docs should name the commands that send them.
Alternatives considered
stop: the server is still running, so the usage values are real, but withstartsending first it would only add a report when a server runs past midnight UTC.details: running it does not mean the server is in use, and anyone who runs it has already installed or started the server.- Leave it as is and say in the docs that only servers running
monitorare counted.
🤖 Generated with Claude Code
- Dominant language
- Shell
- Stars
- 4.9k
- Forks
- 866
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 100
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
GameServerManagers/LinuxGSM#5241 ·
Maintainers usually reply within 1 day
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
GameServerManagers/LinuxGSM#5240 ·
Maintainers usually reply within 1 day
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
GameServerManagers/LinuxGSM#5238 ·
Maintainers usually reply within 1 day
-
engine: null game: Teamspeak 3
Difficulty 3/5 Half a day Newbie friendliness 66/100
GameServerManagers/LinuxGSM#5237 ·
Maintainers usually reply within 1 day
All issues in GameServerManagers/LinuxGSM
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100