[Feature]: Count servers that do not run monitor in LinuxGSM Stats
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 68/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- bash, shell
- Ambito
- analytics, cli, documentation
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- Shell
- Stelle
- 4.9k
- Fork
- 866
- Merge medio
- 17h 58m
- PR unite (30g)
- 100
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di GameServerManagers/LinuxGSM
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
GameServerManagers/LinuxGSM#5242 ·
I maintainer di solito rispondono entro 1 giorno
-
distro: Debian distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
GameServerManagers/LinuxGSM#5241 ·
I maintainer di solito rispondono entro 1 giorno
-
command: send distro: Ubuntu engine: spark game: Natural Selection 2 priority: high scope: single game type: feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
GameServerManagers/LinuxGSM#5240 ·
I maintainer di solito rispondono entro 1 giorno
-
command: monitor distro: Ubuntu engine: spark game: Natural Selection 2 info: query reproducible: unable severity: critical type: bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
GameServerManagers/LinuxGSM#5238 ·
I maintainer di solito rispondono entro 1 giorno
-
engine: null game: Teamspeak 3
Difficoltà 3/5 Mezza giornata Idoneità per principianti 66/100
GameServerManagers/LinuxGSM#5237 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di GameServerManagers/LinuxGSM
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
nolte/claude-goose#18 ·
-
gated_tree trusts assume-unchanged entries, and can leave its temporary directory on a signalApertadecision
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
btclib-org/claude-process#609 · 1 commento ·
-
enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
varnish/helm-varnish#173 ·
I maintainer di solito rispondono entro 2 giorni
-
bump version [nginx2root]Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100