Skip to content

v0.13.5

Choose a tag to compare

@github-actions github-actions released this 20 Oct 23:50
· 744 commits to main since this release

Added

  • "Network ports to open" in every setup guide. Each guide opens with the
    ports to allow, with the direction spelled out (from the DumbMonit server or
    its relay agent to the device; for the agent, the other way round) and the
    ports only an option needs marked optional. The device pages of the
    documentation start with the same table.
  • A quiet note when an optional feature is skipped for a missing permission.
    On Proxmox VE, Proxmox Backup Server and Proxmox Datacenter Manager, a 403 on
    an optional call (guest agent, pending updates, certificate expiry, update
    summary...) no longer vanishes silently: the monitor page says which feature
    was skipped and which permission the token lacks. It never raises an alert.

Fixed

  • Editing a monitor no longer loses or seems to lose its credentials. The
    edit form now shows the saved non-secret parts (Proxmox token ID, user name,
    SNMP v3 user and protocols), returned by the API as credential_public with
    has_secret; a saved secret shows as dots ("Saved. Leave empty to keep it").
    A secret field left blank is now left out of the request and the server keeps
    the saved one, as long as the user name or token ID it belongs to and the
    address are unchanged; otherwise the form asks to type it again. This fixes
    a real loss: editing an SNMP v3 monitor and retyping only the authentication
    passphrase erased the privacy passphrase. Secret fields also no longer invite
    the browser to autofill the DumbMonit sign-in into them. SNMP v3 gains an
    explicit "None" privacy choice to turn encryption off. Secrets are still never
    returned by any response.

Added

  • Server logs: kept on disk, downloadable, and shipped to a log service.
    DumbMonit now writes its own logs (and its audit log entries, marked
    "kind":"audit") to /data/logs, one JSON-lines file per day, compressed
    once the day is over, kept 14 days by default and capped at 1 GB in total
    (both adjustable in Settings → System → Logs). An administrator can
    download the last 1, 7, 14, 30 or any number of days as a .tar.gz, with
    the size shown before the download starts. Logs can also be sent to
    Graylog (GELF over UDP, TCP or HTTP), VictoriaLogs (JSON lines), Grafana
    Loki (push API), Elasticsearch / OpenSearch (bulk API) or any syslog
    receiver (RFC 5424 over UDP, TCP or TLS), each destination with its own
    minimum level and a Send test button. Shipping runs in the background
    with a bounded queue: if a destination is down, records are dropped and
    counted rather than slowing the server. Anything that looks like a secret
    (credentials in a URL, tokens in a query string, Authorization headers)
    is masked before it is written or sent, and the first-run setup code only
    ever goes to the console.
  • Wall widgets: a screen model to arrange them, News folded in, a Text
    widget.
    Settings → Wall widgets now shows a 16:9 model of the wall (top bar,
    right column under the clock, bottom bar, a tray for hidden widgets) where
    widgets are dragged and dropped with a mouse or a finger, or selected and moved
    with the arrow keys and Move to buttons; what is dropped is what /wall
    shows, and Reset to default restores the default layout (on a phone the model
    is an ordered list). The News feeds are now the settings of the News widget
    in the same list, saved with the others; nothing to redo, the configured feeds
    are kept. The new Text widget shows a short free message (plain text, 200
    characters) wherever it is placed.
  • Import Uptime Kuma 1.x and 2.x from kuma.db. Uptime Kuma 2 dropped its
    JSON backup, so the import now also reads the SQLite database
    (docker cp uptime-kuma:/app/data/kuma.db .): upload it, preview the monitors
    sorted by type and folder, tick the ones to import (those already monitored are
    flagged) and import them in one click, with the same mapping as the JSON
    backup. The file is read once in read-only mode from a temporary copy (at most
    512 MB) that is deleted afterwards. Uptime Kuma 2 on MariaDB is not supported.
    New endpoint POST /api/targets/import/kuma-db, and rows= on both Kuma
    import endpoints. See
    Coming from Uptime Kuma.

Changed

  • Add a monitor: the import buttons (Uptime Kuma, websites CSV) moved from the
    top of the page to a new Import category at the bottom, beside
    Everything else.
  • Relay mode is switched from the UI. An agent's page has a Relay for a
    remote site
    switch and a site field: the server sends the setting to the
    agent in its next acknowledgement and the agent turns relay mode on or off on
    the fly, without a restart or a file to edit. relay: true in agent.yaml
    still wins; an agent too old to follow the switch is flagged. A token from
    Watch a remote site (or with This agent is a relay for a remote site
    ticked) carries relay mode and the site, so the enrolled agent is a relay
    from its first report. Once a relay, its page links to Scan this site's
    network
    and Add a monitor through this relay.
  • Reached through, in bulk. The monitors list's selection bar sets Reached
    through
    (direct or a relay) on many monitors at once, skips agent monitors
    with a note, and offers to place them at the location whose site is the
    relay's.

Changed

  • Simpler setup guides when adding a monitor. Each guide is now a few short
    steps done in the product's own web interface (a command is kept only where
    the product has no interface for it), followed by a framed "Required
    permissions" list with the exact rights, roles or scopes to grant, and a
    "Full guide" link to the matching documentation page. The device pages of the
    documentation carry the same steps and permissions. Integration packs can list
    setup.permissions too.

Added

  • Dismiss an alert in one click. Every alert now leads with a Dismiss
    button — in the alert list, an alert's details and a monitor's panel — with
    no duration to pick and no confirmation, only a toast with Undo. A
    dismissed alert leaves the active list, the overview, the wall and every
    counter, and nothing more is sent for it (no reminder, no escalation, no
    resolution message) for as long as the condition lasts. The dismissal belongs
    to that occurrence: once the condition clears, a later return is a new alert,
    notified as usual. Its resolution stays in the history as "dismissed by …",
    and a Dismissed view lists the ones still active, to restore a mistake.
    Acknowledge and Snooze stay available in the alert's … menu.
    Notifications carry a Dismiss link first ({{dismiss_url}} for custom
    webhooks), the API gains POST/DELETE /api/alerts/{fingerprint}/dismiss
    and GET /api/alerts?dismissed=true, and assistants a dismiss_alert tool.

Changed

  • The folded group of acknowledged alerts in the Now list is called
    Acknowledged (it read Dismissed).
  • Active Directory: DNS servers option. When the DumbMonit host's DNS does
    not know the domain, fill DNS servers with the IPs of the servers that do:
    every name lookup of the monitor (the controller you entered, the other
    controllers, the reachability check) goes through them over UDP then TCP,
    while LDAPS still checks the certificate against the name. Empty keeps the
    system resolver; works through a relay agent too.

Fixed

  • A remote-site relay installs in one command. An agent installed from
    Settings → Agents → Watch a remote site was not a relay until relay: true
    was added to agent.yaml by hand. Its token now makes it a relay (see above),
    and the agent.yaml step is only a folded note for agents already installed.
    The install scripts also accept --relay and --site=NAME (-Relay -Site NAME on Windows) for a relay set on the machine itself.