MythEclipse/GMW
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(gateway): correct metrics port — 4016 was wrong

Browse Source 
The metrics server binds METRICS_PORT (code default 9090; this host runs it
on 4018 — 4016 is occupied by another process). Docs said 4016 in three
places, which is not what the service does.
This commit is contained in:
asepharyana
2026-09-24 15:50:15 +07:00
parent c57ee12da1
commit 750f3aa598
2 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
services/discord-gateway/ARCHITECTURE.md
+6 -4
View File
@@ -43,7 +43,7 @@ services/discord-gateway/
│ ├── command-handler/ # Redis-subscribed backend→gateway commands │ ├── command-handler/ # Redis-subscribed backend→gateway commands
│ ├── reaction-tracking/ thread-tracking/ user-presence/ │ ├── reaction-tracking/ thread-tracking/ user-presence/
│ ├── channel-topic/ guild-member-events/ monitor/ │ ├── channel-topic/ guild-member-events/ monitor/
│ └── gateway-metrics/ # Prometheus /metrics endpoint (port 4016) │ └── gateway-metrics/ # Prometheus /metrics endpoint (METRICS_PORT)
``` ```
Dependency direction is one-way: `index.ts` → `app/` → `modules/` → `shared/`. Dependency direction is one-way: `index.ts` → `app/` → `modules/` → `shared/`.
@@ -148,8 +148,8 @@ See `src/shared/redis-channels.ts` for the canonical names.
`initializeDatabase()` (pg Pool, min 0). `initializeDatabase()` (pg Pool, min 0).
4. `registerClientDebugLogging()` — only client debug lines carrying signal. 4. `registerClientDebugLogging()` — only client debug lines carrying signal.
5. Install process guards (`registerProcessGuards`). 5. Install process guards (`registerProcessGuards`).
6. Register pipeline gauges + start the metrics server (port `METRICS_PORT`, 6. Register pipeline gauges + start the metrics server (`METRICS_PORT`, code
default 4016). default 9090, set per deployment).
7. `client.login(token)`. 7. `client.login(token)`.
On the Discord `ready` event, `lifecycle.ts` runs `startGatewayLifecycle()`: On the Discord `ready` event, `lifecycle.ts` runs `startGatewayLifecycle()`:
@@ -173,7 +173,9 @@ handler → close DB → destroy client → exit.
## Observability ## Observability
Prometheus scrapes `127.0.0.1:4016/metrics` (`bete_*` prefix). Collectors run Prometheus scrapes the metrics server at `127.0.0.1:$METRICS_PORT/metrics`
(`bete_*` prefix; the code default is 9090 — deployments set it explicitly,
this host uses 4018). Collectors run
per-scrape and expose: process memory/uptime, and (when AI analysis is on) live per-scrape and expose: process memory/uptime, and (when AI analysis is on) live
pipeline gauges registered by `app/metrics-collector.ts` — pipeline gauges registered by `app/metrics-collector.ts` —
`ai_analysis_queued_conversations`, `ai_analysis_active_batch_requests`, `ai_analysis_queued_conversations`, `ai_analysis_active_batch_requests`,
services/discord-gateway/README.md
+1 -1
View File
@@ -47,7 +47,7 @@ src/
├── attachment-upload/ # download → resize → upload ├── attachment-upload/ # download → resize → upload
├── event-broadcaster/ # Redis pub/sub publisher ├── event-broadcaster/ # Redis pub/sub publisher
├── command-handler/ # backend → gateway commands over Redis ├── command-handler/ # backend → gateway commands over Redis
├── gateway-metrics/ # Prometheus /metrics (port 4016) ├── gateway-metrics/ # Prometheus /metrics (METRICS_PORT)
├── monitor/ # weekly digest scheduler ├── monitor/ # weekly digest scheduler
└── reaction-tracking/ thread-tracking/ user-presence/ └── reaction-tracking/ thread-tracking/ user-presence/
channel-topic/ guild-member-events/ channel-topic/ guild-member-events/