fix(monitoring): comment-out mana-ai metrics scrape after Phase 2f-3 move

mana-ai's /metrics endpoint is no longer exposed on Mini's
192.168.178.131:3067 (service moved to GPU-Box, no public /metrics
tunnel since the endpoint is internal). The blackbox-api job
already probes mana-ai.mana.how/health for liveness, which gives
us up/down without needing the metrics scrape.

Status-page is now 58/58 UP after VM rolled past the stale 3067
samples.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Till JS 2026-05-07 17:06:04 +02:00
parent dcd16067b5
commit a8cce79e4c

View file

@ -123,14 +123,8 @@ scrape_configs:
metrics_path: '/metrics'
scrape_interval: 30s
# Mana AI Service (Bun) — background Mission Runner for the AI Workbench.
# Exposes tick stats, planner-request latencies, snapshot refresh
# counters, and standard HTTP metrics at /metrics.
- job_name: 'mana-ai'
static_configs:
- targets: ['mana-ai:3066']
metrics_path: '/metrics'
scrape_interval: 30s
# SKIPPED Phase 2f-3 — mana-ai moved to GPU-Box; no public /metrics endpoint via tunnel.
# blackbox-api probt mana-ai.mana.how/health stattdessen.
# Mana MCP Gateway (Bun, :3069) — exposes the shared tool-registry
# over Streamable HTTP to external agents. Emits policy-gate