Pingtower
Docs
logwatch
Tail a local file for a pattern. Counts matches, notices rotation, and never sends a line off the box.
privileged Add logwatch to agent.enable_addons, and give the addons user read access to the file.
A logwatch check runs only from the agent’s local config, because its path names a file on the box itself. The agent refuses a logwatch check that Pingtower assigns to it, even when enable_addons names the addon: it logs assignment rejected, counts the assignment as rejected, and runs the rest of its checks. The API refuses with a 400 to create one, to change one’s with, or to switch a check to either addon, and the MCP create and update tools refuse it too. A logwatch check stored in Pingtower before Release 1 is kept but no longer assigned to any agent: reading it shows paused with the reason local_only. Move it into the agent’s config and delete it there, as Upgrading to Release 1 describes.
Parameters
| Parameter | Default | Meaning |
|---|---|---|
pathREQUIRED | ||
patternREQUIRED | RE2. | |
warn_at | 1 | Matches per run at or above this are degraded. |
down_at | 0 | Matches at or above this are down. 0 means never. Wins over warn_at. |
max_bytes | 4 MiB | Most read per run; the rest is reported as skipped_bytes. |
initial_tail | 256 KiB | How far back to read on first run. |
A missing file is down. An unreadable one is a config error.
Measurements
matches, lines_scanned, bytes_scanned, skipped_bytes, last_write_age_s, rotated, cold_start.