Observability blind spots found in the 11-12 live investigation (item ledger, history retention, alerts)
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 12/100
- Type d'issue
- Fonctionnalité
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- go, sqlite
- Domaine
- backend, observability
Piste de recherche
This is a multi-part design issue, not a single change. Start with the hourly bucket code behind npc_sale and monster_gold, then the economy_ledger writer and the history.sqlite pruner, and read #3302 for the census index. Done when each checklist box is a merged change or a recorded decision not to do it.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
The 2026-11-12 live investigation (#3302, #3303 and the starter-refill issue) had to infer facts the server should record. Each line is data we lacked; fix them so the next investigation reads facts instead of joining timestamps.
Items
- No item ledger. Gold has
economy_ledger; items have nothing. A grant (starter kit, refill, quest, GM, mall, drop pickup), a merchant sale, a stall or exchange transfer and a destroy leave no row saying which item, how many, and through which door. A duplication cannot be proved or cleared after the fact without diffing nightly backups. -
npc_saleandmonster_goldfold into hourly buckets holding onlytotalandn. The item sold is lost at once. Keep a per-character, per-item hourly bucket (item ref, count, gold). -
stall_saleandexchangerows name no counterparty and no item. Finding who paid 1,000,000,000 to whom, and for what, took a self-join onat_ms. Record the counterparty character and the items on both sides.
Sessions
-
history.sqlitekept only about 90 minutes: two accounts wrote most of 200k events (every transport log line of every session becomes an event) and the pruner dropped everyone's older history. Budget events per account, and do not store per-session transport info lines as history events. - GameWorld and Agent logs live only in the Nomad alloc and vanish at the next release. Ship them to durable storage with a retention rule (they hold player names, so staff-only).
- The Agent logs only refused admission tickets. Count minted tickets per account (a counter and a journal column), so a mint rate is visible.
- The connection journal has no per-session summary of what the session did: frames in, opcodes used, time to first action. "Entered, sold, left in one second" was inferred from three stores.
Detection
- Nothing alerted.
account_session_evictionsreached 74k, one account opened 3 sessions a second for a day, and 97% of the connection journal came from four accounts. The monitor needs rate alerts: sessions per account per minute, evictions per minute, entries per character per hour, merchant sales per entry. - A websocket session with no User-Agent is not a browser (every browser sends one). It is recorded and never surfaced. Show it in the console and count it.
- The console has no "top accounts by session churn / by minted gold per hour" view; the hourly buckets already hold the gold half.
- Every free grant (kit, refill, beta silk, starter silk) needs a counter per account per day, so a mint shows as a number that grows.
Performance of the tools themselves
- The census index is quadratic in sessions per account (#3302), so the abuse it should expose degrades the server.
Done when each box is a merged change or a recorded decision not to do it.
- Langage dominant
- Go
- Étoiles
- 97
- Forks
- 61
- Merge moyen
- 4 h 14 min
- PR mergées (30 j)
- 913
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de opensro-dev/opensro
-
area: client enhancement priority: low
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
opensro-dev/opensro#3681 ·
Les mainteneurs répondent en général sous 1 jour
-
area: client bug priority: low
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
opensro-dev/opensro#3228 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Format one minified client file with dprint (ongoing: one file per PR)Peut-être pris Une pull request liée à cette issue est ouverte ou déjà fusionnée. Ouvertearea: client enhancement good first issue priority: low
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
opensro-dev/opensro#1 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
area: server bug priority: medium
Difficulté 3/5 Une demi-journée Accessibilité débutants 55/100
opensro-dev/opensro#3687 ·
Les mainteneurs répondent en général sous 1 jour
-
area: ops bug priority: high
Difficulté 4/5 3-5 jours Accessibilité débutants 32/100
opensro-dev/opensro#3685 ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de opensro-dev/opensro
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
unbound-force/gaze#353 ·
Les mainteneurs répondent en général sous 1 jour
-
bug cross-seed ready-for-human
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 64/100
OneBusAway/maglev#2102 ·
Les mainteneurs répondent en général sous 2 jours
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soOuverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Les mainteneurs répondent en général sous 1 jour