abiba-bot/prose-contracts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

prose: fix proxmox-monitor access to direct :3001 (revert sub-path)

Browse Source 
Revert the /grafana/ nginx sub-path I wrongly added — it broke the existing
http://192.168.68.116:3001/d/gpu-fleet URL. Restored direct 0.0.0.0:3001 LAN
access. Contract is now the source of truth: no GF_SERVER_SERVE_FROM_SUB_PATH,
no nginx /grafana/ route. gpu-fleet + 3 new dashboards all at :3001.
This commit is contained in:
root
2026-07-02 02:56:27 +00:00
parent 4df2fa8329
commit 3700b3bf46
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
proxmox-monitor.prose.md
+5 -6
View File
@@ -16,7 +16,7 @@ agent: abiba
``` ```
┌─────────────────────────────────────────────────────────────┐ ┌─────────────────────────────────────────────────────────────┐
│ CT 116 (syslog-api) — monitoring compose /opt/monitoring/ │ │ CT 116 (syslog-api) — monitoring compose /opt/monitoring/ │
│ Prometheus :9090 → Grafana :3001 (nginx /grafana/) │ │ Prometheus :9090 → Grafana :3001 (direct LAN, 0.0.0.0) │
└───────┬──────────────┬──────────────┬───────────────────────┘ └───────┬──────────────┬──────────────┬───────────────────────┘
│ │ │ │ │ │
▼ ▼ ▼ ▼ ▼ ▼
@@ -60,11 +60,11 @@ agent: abiba
## Access ## Access
- **URL**: `http://192.168.68.116/grafana/` (LAN, via nginx sub-path) - **URL**: `http://192.168.68.116:3001/` (LAN, direct — Grafana bound to `0.0.0.0:3001`)
- **Dashboards**: `http://192.168.68.116:3001/d/gpu-fleet`, `.../d/proxmox-cluster`, `.../d/proxmox-node`, `.../d/docker-containers`
- **Credentials**: admin / syslog-grafana-2026 - **Credentials**: admin / syslog-grafana-2026
- nginx route: `/opt/inference-harness/nginx/nginx.conf` `location /grafana/` → `proxy_pass http://harness-grafana:3000;` (no trailing slash — preserves prefix for serve_from_sub_path) - Grafana is NOT behind nginx — access port 3001 directly. The `harness-nginx` `/grafana/` sub-path route was tried and reverted (broke the existing `:3001` URL and gpu-fleet path). Do not re-add `GF_SERVER_SERVE_FROM_SUB_PATH` or an nginx `/grafana/` route.
- harness-nginx connected to `monitoring_default` network (`docker network connect monitoring_default harness-nginx`) - grafana compose port mapping: `"3001:3000"` (0.0.0.0, not 127.0.0.1)
- grafana env: `GF_SERVER_ROOT_URL=http://192.168.68.116/grafana/`, `GF_SERVER_SERVE_FROM_SUB_PATH=true`
## Configuration Files ## Configuration Files
@@ -77,7 +77,6 @@ agent: abiba
| `/opt/monitoring/grafana/dashboards/build-dashboards.py` | .116 | dashboard JSON generator | | `/opt/monitoring/grafana/dashboards/build-dashboards.py` | .116 | dashboard JSON generator |
| `/opt/monitoring/grafana/dashboards/json/*.json` | .116 | provisioned dashboard definitions | | `/opt/monitoring/grafana/dashboards/json/*.json` | .116 | provisioned dashboard definitions |
| `/opt/monitoring/grafana/datasources/prometheus.yml` | .116 | datasource provisioning | | `/opt/monitoring/grafana/datasources/prometheus.yml` | .116 | datasource provisioning |
| `/opt/inference-harness/nginx/nginx.conf` | .116 | `/grafana/` reverse proxy route |
| `/etc/default/prometheus-node-exporter` | .5/.6/.9/.12/.15 | node_exporter collector config | | `/etc/default/prometheus-node-exporter` | .5/.6/.9/.12/.15 | node_exporter collector config |
## Cluster "Tabiri" — 5 Nodes ## Cluster "Tabiri" — 5 Nodes