---
title: X
description: Setting up the agent on a server with dozens of mounts or interfaces meant guessing names before you could narrow what it watches. The installer now writes…
canonical: https://watchfor.io/changelog/2026-09-17-agent-config-detect
---

[All updates](/changelog/page/3#2026-09-17-agent-config-detect) ⚡ Improved Sep 17, 2026 · v 7.9.9

# Agent config that shows what it found

Setting up the agent on a server with dozens of mounts or interfaces meant guessing names before you could narrow what it watches. The installer now writes agent.yml with every key explained and the mounts, disks and interfaces it found listed inside, so you edit a list instead; watchfor-agent config detect prints the same on demand. New: facts.cloud_metadata to switch off the cloud instance-size lookup, and log.level debug to see every push and lookup in the journal.

## The problem

A database server can have dozens of mounts (snap loops, bind mounts, a backup volume) and several interfaces. To tell the agent "only watch / and /data ", you first had to dig the exact names out of df and ip , then type them into a file you had never seen before.

## What the file looks like now

The installer writes /etc/watchfor-agent/agent.yml with a comment on every key, and next to each list it puts what it found on this machine. The disk part of a fresh file reads like this:

disk: {} # usage per mount, I/O per whole disk
# Found on this machine: / (ext4, 79 GB), /boot (ext4, 974 MB), /data (xfs, 1863 GB)
# Watch only some of them by listing the mount points (…):
# mounts: [/, /boot, /data]

To watch only the root and data volumes, remove the # from the mounts line and delete /boot . Interfaces work the same way, with their addresses shown so you can tell eth0 from eth1 .

## On demand

watchfor-agent config detect prints the same findings at any time: CPU, memory, hardware, mounts, disks and interfaces. It's useful after you add a disk.

## Two new switches

- facts.cloud_metadata: false stops the agent from ever asking a cloud metadata service for the instance size.

- log.level: debug writes every push and lookup to the journal, so you can see exactly what the agent does.

See [Configuration](/docs/hosts#configuration) for every key.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-17-agent-config-detect · Site guide: https://watchfor.io/llms.txt