@ultimat3/core 1.1.0 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +7 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -194,6 +194,13 @@ process cannot drift apart:
|
|
|
194
194
|
| `ws-connections` | `connections` | gauge, `+1`/`-1` |
|
|
195
195
|
| `queue-depth` | `queue_depth` | gauge, by `queue` label |
|
|
196
196
|
|
|
197
|
+
`As of 2026-08` all three are emitted and scraped. One call site per package — `recordRequest`
|
|
198
|
+
from `@ultimat3/http`'s pipeline, `recordConnection` from `@ultimat3/realtime`'s socket table,
|
|
199
|
+
`recordQueueDepth` from `@ultimat3/jobs`' worker loop — and `@ultimat3/cli` serves `metricsText()`
|
|
200
|
+
at `METRICS_PATH` on `METRICS_PORT` (9090), for every role rather than only the ones that open an
|
|
201
|
+
HTTP socket. Labels are route **patterns**, status **classes** and queue names: nothing
|
|
202
|
+
per-user, per-id or attacker-chosen ever becomes a series.
|
|
203
|
+
|
|
197
204
|
## One cursor, everywhere
|
|
198
205
|
|
|
199
206
|
```ts
|