HLS su edge e monitoraggio ops con latenza p95.

Evita di saturare Puma in diretta, separa i check Rails/pubblico e traccia la latenza /up per alert più affidabili.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-06-14 21:19:32 +02:00
parent 13390d8a3c
commit a44d9fbadd
11 changed files with 290 additions and 52 deletions

View File

@@ -73,6 +73,14 @@ REPLAY_MEDIA_REDIRECT=true
# Puma: 5 thread (no secondo worker senza più RAM)
RAILS_MAX_THREADS=5
# Ops — check Rails via edge (critical) + percorso pubblico (warning, ogni 15 min)
OPS_HTTP_RAILS_URL=http://edge/up
OPS_HTTP_PUBLIC_INTERVAL_SECS=900
OPS_UP_LATENCY_WARN_MS=2000
OPS_UP_LATENCY_CRIT_MS=5000
OPS_UP_LATENCY_SAMPLES=60
OPS_UP_LATENCY_MIN_SAMPLES=5
# Ops monitoring — notifiche push (ntfy self-hosted) e health check
# 1) Avvia servizio: docker compose up -d ntfy
# 2) NPM: proxy HTTPS → http://192.168.1.146:8090 (es. ntfy.matchlivetv.it, WebSockets ON)