DumbMonit

IntégrationsServeurs et machines

Server with agent

Linux, Windows, macOS or FreeBSD: CPU, memory, disks, network, Docker, services, backups.

Documentation

Les descriptions des produits sont en anglais, comme dans le produit. Les libellés de la page suivent votre langue.

Ce que DumbMonit surveille

A small binary installed on the machine to monitor. It measures CPU, memory, disks, network, services and containers — and, where the machine exposes them, temperatures, disk health, ZFS pools and KVM virtual machines — then pushes its readings to the DumbMonit server over HTTPS, on an encrypted channel of its own (see Agent channel security).

Usage typique. Linux, Windows, Raspberry Pi, Hyper-V host

Exemples

  • Linux server
  • Windows server
  • Raspberry Pi

Comment il se connecte

Aucun compte nécessaire.

Ports réseau à ouvrir

  • 8443/TCPReadings and commands: the encrypted agent channel (TLS 1.3 and a client certificate)
  • 8080/TCPInstall script and agent download, at install and update time (HTTPS; 443 behind a reverse proxy)
Étapes de mise en place: Install the agent on the machine
  1. In DumbMonit, add a monitor and pick Server with the agent, then choose how the machine reaches the server: directly, or through the relay of a remote site behind a firewall.

  2. An enrollment token (its secret starts with dmon_; the token is listed as tok_… afterwards) is shown once, with the install command ready to copy for Linux/macOS, Windows and Docker.

  3. Run that install command on the machine, with elevated rights (sudo on Linux and macOS, an elevated PowerShell on Windows).

  4. The page waits for the first report (a few seconds), then lets you name the machine, file it in a folder and place it at a site, on the spot.

  5. Optional, for Docker: if the agent runs under a dedicated user, add that user to the "docker" group and restart the agent.

    usermod -aG docker dumbmonit
  6. For a fleet (a playbook, a machine image), tick Several machines with this command; a whole Windows domain goes through the Active Directory kit, offered on the same page.

À savoir. The agent contacts the server, never the other way round: no port needs to be opened on the monitored machine.