bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(devops): note admin ops inventory and valkey panel

Browse Source
This commit is contained in:
root 2026-03-31 08:32:50 +00:00
parent bd7ebeb248
commit 23d5ef44f3
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/devops/single_azure_vm/docker/DEPLOYMENT_STATUS_2026-03-29.md
View File

@ -16,6 +16,7 @@ The VM moved forward after the original snapshot:
- `prometheus`, `node-exporter`, `cadvisor`, and `valkey` are now running - `prometheus`, `node-exporter`, `cadvisor`, and `valkey` are now running
- `admin-web` and `tracker-web` are healthy again - `admin-web` and `tracker-web` are healthy again
- `extraction-service` product rate limiting now uses Valkey-backed shared counters - `extraction-service` product rate limiting now uses Valkey-backed shared counters
- the admin ops page now includes VM inventory and Valkey inspection panels
- live verification confirmed a request for `productId=valkey-check-2` created the key `extraction:product-rate-limit:29582406:valkey-check-2` in Valkey with value `1` - live verification confirmed a request for `productId=valkey-check-2` created the key `extraction:product-rate-limit:29582406:valkey-check-2` in Valkey with value `1`
### What is working ### What is working

11
docs/devops/single_azure_vm/docker/README.md
View File

@ -179,6 +179,7 @@ Notes:
- neither `prometheus` nor `valkey` needs a raw public port exposure for normal operation - neither `prometheus` nor `valkey` needs a raw public port exposure for normal operation
- `extraction-service` now uses Valkey for shared per-product rate limiting when `PRODUCT_RATE_LIMIT_STORE=valkey` - `extraction-service` now uses Valkey for shared per-product rate limiting when `PRODUCT_RATE_LIMIT_STORE=valkey`
- `extraction-service` falls back to its in-memory limiter only if Valkey is unavailable at runtime - `extraction-service` falls back to its in-memory limiter only if Valkey is unavailable at runtime
- the admin Mission Control page now includes a VM inventory tab and a read-only Valkey inspector tab
### Shared limiter env ### Shared limiter env
@ -199,6 +200,16 @@ docker exec learning_ai_common_plat-valkey-1 \
valkey-cli KEYS 'extraction:product-rate-limit:*' valkey-cli KEYS 'extraction:product-rate-limit:*'
``` ```
### Admin ops surface
The internal admin dashboard at `http://<vm-ip>:3001/ops` now exposes:
- Mission Control health for the internal stack
- a VM inventory view of Docker-managed services and host tooling
- a read-only Valkey inspector for key pattern scans, TTLs, and small previews
These views are protected by the admin dashboard auth layer.
## Environment Variables ## Environment Variables
All optional — defaults work for most setups: All optional — defaults work for most setups: