Skip to content

v1.5.5.7

Choose a tag to compare

@github-actions github-actions released this 25 Jun 11:22

Thanks to @Inch-high for the detailed follow-up on #12 — network and disk telemetry on Unraid needed more than settings normalization.

What changed

  • templates/amud-agent.xml — AMUD Agent uses host network by default; optional read-only Array (/mnt/user) and Cache (/mnt/cache) bind-mounts for disk mapping
  • docker-compose.yml — commented network_mode: host and bind-mount examples for production telemetry
  • amud-agentAMUD_PROC_NET_DEV, telemetry_scope, visible iface/mount lists, bond/zero-traffic heuristic, per-mount disk_volumes, telemetry_discover action
  • amud-protocolDiskMountTelemetry and new AgentTelemetry fields
  • amud-server/api/telemetry/discover for Settings Test host visibility
  • Dashboard UI — separate disk tile per configured mount; (container scope) / (auto-detect) admin hints
  • Docs — Unraid Step 3b, expanded troubleshooting decision tree

Install / Upgrade

Proxmox / bare metal:

curl -sSL https://github.com/boubli/AMUD-Dashboard/releases/latest/download/update-amud.sh | bash

Docker / Unraid:

docker compose pull && docker compose up -d --force-recreate

On Unraid: Force Update both AMUD-Dashboard and AMUD-Agent, re-apply agent template (host network + array/cache mounts), then hard-refresh (Ctrl+Shift+R). Use Settings → Test host visibility to confirm Scope: host.