ProxMenux LogoProxMenux

Post-Install: Monitoring

Settings post-install Proxmox

Monitoring options inside the Customizable post-install script. This category is small and provider-specific — it installs the OVH Real-Time Monitoring agent on dedicated OVH servers and does nothing anywhere else.

Narrow scope on purpose

Post-install monitoring is limited to one provider-specific agent. General-purpose monitoring (Prometheus, Grafana, node_exporter) is out of scope here because those require architectural decisions (separate host or not, data retention, alerting targets) that don't fit a one-click post-install step. ProxMenux Monitor itself, bundled with ProxMenux, fills most of that role without needing any external agent.

Install OVH Real-Time Monitoring (RTM)

If your Proxmox host is a dedicated server rented from OVHcloud, you can enable RTM to expose hardware telemetry (CPU temperature, PSU status, disk SMART, RAID controller state, etc.) to the OVH control panel. This is the same agent OVH uses for their own "Server Monitoring" feature.

How ProxMenux decides

  1. Gets the host's public IP via curl ipinfo.io/ip.
  2. Looks up the owning ISP with a whois query to v4.whois.cymru.com.
  3. If the result mentions OVH, fetches last-public-ovh-infra-yak.snap.mirrors.ovh.net/yak/archives/apply.sh and pipes it to bash with the RTM v2 puppet manifest.
  4. If the result does not mention OVH, nothing is installed. The option is a no-op.

Remote script piped to bash

The installation runs wget -qO - https://…apply.sh | bash. If the OVH mirror is ever compromised, the script executes as root on your host. Before enabling this option, decide whether you trust OVH's mirror chain more than the monitoring you gain. For most home-lab or non-OVH users this option should simply stay off.

Only enable if the host is actually at OVH

The option is a no-op on non-OVH servers, so ticking it on a home-lab Proxmox doesn't break anything. But there is a cosmetic bug today: even on non-OVH servers the script prints "Server belongs to OVH" at the end, which can be misleading. See the troubleshooting note below.

What ProxMenux runs

# Detect + conditionally install
public_ip=$(curl -s ipinfo.io/ip)
is_ovh=$(whois -h v4.whois.cymru.com " -t $public_ip" | tail -n 1 | cut -d'|' -f3 | grep -i "ovh")

if [ -n "$is_ovh" ]; then
  wget -qO - https://last-public-ovh-infra-yak.snap.mirrors.ovh.net/yak/archives/apply.sh \
    | OVH_PUPPET_MANIFEST=distribyak/catalog/master/puppet/manifests/common/rtmv2.pp bash
fi

Verification

On a real OVH host, after a reboot you should see the RTM dashboard in your OVH Manager populated with live data for the host. On the Proxmox side, the RTM collector is a systemd service — check it directly:

systemctl status ovh-rtm      # or grep the unit name from your install log
journalctl -u ovh-rtm --since "10 min ago"

Troubleshooting

"Server belongs to OVH" but I'm not on OVH

This is a known cosmetic quirk in the current script: the success message fires outside the OVH-detected conditional, so it prints on every run. If the RTM install did not actually happen (check systemctl status ovh-rtm — it will not exist), the message is spurious and can be ignored. Nothing was installed on your host.

Not reversible from the Uninstall menu

There is no dedicated uninstall entry for RTM. On a real OVH host, remove the packages manually with apt purge ovh-* and delete any puppet manifests under /etc/puppet/ that RTM installed. On a non-OVH host, nothing was ever installed, so there's nothing to revert.

Related

ProxMenux Scripts: Previous
Customization
ProxMenux Scripts: Next
Performance