Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

monitoring-alerting

/monitoring-alerting

Monitoruje routery i flotę, zgłaszając tylko zmiany: sondy netwatch, progi i powiadomienia.

Repozytorium
routeros-muse ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Monitoruje routery i flotę, zgłaszając tylko zmiany: sondy netwatch, progi i powiadomienia.

Oryginalny opis (EN)

Watch the boxes and speak only on change: what to read, netwatch up/down/recovery probes, threshold checks, notify-on-change discipline. Use when: setting up monitoring for a router or fleet, adding a netwatch probe, choosing thresholds, wiring notifications, or asking what healthy looks like.

Jak działa

  1. Part 1 — The checklist (prove the probe before trusting it)
  2. Part 2 — Skill doc
Sekcje z nagłówków SKILL.md, w oryginale · 232 linii, 1 393 słów
Podgląd SKILL.md
---
name: monitoring-alerting
description: "Watch the boxes and speak only on change: what to read, netwatch up/down/recovery probes, threshold checks, notify-on-change discipline. Use when: setting up monitoring for a router or fleet, adding a netwatch probe, choosing thresholds, wiring notifications, or asking what healthy looks like."
topics: [monitoring]
requires: [twin]
tested: none
---

# `monitoring-alerting` skill (reads → probes → thresholds → notify-on-change) [template v1 draft]

Promoted from the executed netwatch flap drill
(a 7.26beta3 CHR twin: up + down + recovery
scripts all fired and logged) plus the look-after chain
(collect/investigate/notify cadences,
hysteresis, dedup, recovery announce, failed-never-green).
The SCHEDULED LOOP and the notify TRANSPORTS (mail,
webhook, push) are prescribed, not executed — what IS proven
is the on-box probe mechanics and the read inventory. Complements
the look-after loop (unbuilt) and
service-path-fleet-check (the fleet view); this skill is the
single-box watch. No secrets below.

## Part 1 — The checklist (prove the probe before trusting it)

Run top to bottom. No alert the owner sees should rest on a
probe that never fired on a twin.

1. Inventory the reads: confirm which watch-menus answer on
   THIS box (resource, logs, netwatch, packages — step 0).
   CHR lacks sensors; hardware lacks nothing but costs flash.
2. Stage the probe on a twin: netwatch host + up/down log
   scripts, short interval AND short startup-delay (step 1).
3. Fire all three transitions: down (unreachable host), up
   (gateway), recovery (flip dead→live). All three must log
   before the probe shape is trusted (step 2).
4. Set thresholds with hysteresis: alert value, clear value,
   and the dedup window — never a single trip line (step 3).
5. Wire notify-on-change only: collection runs often,
   investigation on state change, notification on
   transitions + recovery. Steady-state is silent (step 4).

### 0. What to watch (the read inventory)

Grounded reads (all ran on the twin unless noted):

- `/system/resource/print` — uptime, load, free-memory,
  free-hdd-space. The liveness heartbeat; poll it first,
  always. (Observed on every twin readiness check.)
- `/log/print [where ...]` — the box's own event stream.
  Probe scripts land here (`script,info` /
  `script,warning`); config changes self-log
  (`Netwatch config added by api:...` observed). Logs are
  append-only: drill lines persist, which is evidence, not dirt.
- `/tool/netwatch/print` — probe states (`up`/`down`/
  `unknown`) + the `.about` startup-delay warning. Read
  after any netwatch change: `unknown` + the warning means
  "waiting", not "broken".
- `/system/package/print` — installed versions; the drift
  input for upgrade planning (backup-restore-upgrade).
- `/system/health/print` — hardware sensors. On CHR it
  answers `{"state":"disabled"}` (proven this session):
  no sensors, no data. On hardware this menu is the
  temperature/voltage/fan watch — but confirm it answers
  before building thresholds on it.
- `/interface/print stats` + firewall counters (firewall-apply) — the
  traffic half: counters that should move and don't are a
  signal (stuck queue, dead peer).

NOT watched from here: dude DB internals, UM rows, file
bytes — those are pull/ + coverage-audit (backup-restore-upgrade) territory.

### 1. Netwatch probes (writes — twin first, always)

```sh
centrs execute --quickchr <twin> '/tool/netwatch/add host=10.0.2.2 interval=10s startup-delay=5s up-script=":log info t28-nw-up-gw" down-script=":log warning t28-nw-down-gw" comment="t28-nw-gw"' --yes
# -> {"ret": "*1"}
```

- Grounded end to end: two hosts added
  (gateway + unrouted), states read back, scripts fired,
  tagged cleanup to `{}`.
- `startup-delay` defaults to 5 MINUTES: fresh probes sit at
  `status: unknown` with a `.about` warning and fire
  nothing until it elapses (observed verbatim). For drills
  set `startup-delay=5s`; for production set it
  deliberately (post-reboot flapping vs time-to-first-
  probe) and record the choice.
- Script bodies stay single-token-log simple:
  `:log info <marker>` / `:log warning <marker>`. No
  quoting gymnastics across the transport; the marker
  carries the meaning (`t28-nw-down-dead` beats a
  sentence). Escalation (mail, webhook) hangs off the
  log/topic layer or the loop — not inside the probe.
- Tag every probe (`comment=`): rollback is
  `remove [find comment~"<tag>"]` + re-print, same as firewall-apply.

### 2. Fire all three transitions (writes — the trust step)

```sh
# down:  host=10.255.255.1 (unrouted)  -> status down,  :log warning fires
# up:    host=10.0.2.2 (gateway)        -> status up,    :log info fires
# flap:  set [find comment="<tag>-dead"] host=10.0.2.2  -> up-script fires = RECOVERY
centrs execute --quickchr <twin> '/log/print where message~"<marker>"'  # read back all three
```

- Grounded: `t28-nw-up-gw` 20:21:28,
  `t28-nw-down-dead` 20:21:31, `t28-nw-up-dead` (recovery)
  20:21:58 — down, up, and recovery all logged on the twin.
- The recovery flip is the load-bearing test: a probe that
  pages on down but stays silent on recovery trains the
  owner to ignore it. "Announce recovery" is this
  line. Every probe shape proves recovery before it ships.
- Unknown is not down: `status: unknown` during
  startup-delay must NEVER page. The loop treats unknown
  as "waiting" (failed-never-green cuts the other
  way too — pending is not verdict).

### 3. Thresholds with hysteresis (prescribed shape, proven reads)

```sh
# Shape (scheduler + script; prescribed — no scheduler drill ran yet):
#   :local free [/system/resource/get free-memory]
#   :if ($free < <alert-bytes>) do={:log warning "<tag>-lowmem"}
#   :if ($free > <clear-bytes>) do={:log info "<tag>-mem-ok"}   # separate clear line
```

- Two lines, not one: the alert value trips, the HIGHER
  clear value resets. A single trip line flaps on every
  boundary crossing and spams the owner — hysteresis is
  the difference between monitoring and noise.
- Reads feeding thresholds are the step-0 inventory
  (free-memory, cpu-load, free-hdd-space, package
  versions). The scheduler/script mechanics are standard
  RouterOS (routeros-scripting) but UNEXECUTED here —
  the first threshold drill updates this skill.
- Dedup window: the loop, not the probe,
  collapses repeats. Probe says it every interval; the
  loop notifies once per state episode. Don't throttle
  the probe to fix loop spam.

### 4. Notify on change only (prescribed loop)

- Three cadences, separated: COLLECT often (cheap
  reads, every few minutes), INVESTIGATE on state change
  (richer reads only when something moved), NOTIFY on
  transitions + recovery. Steady-state produces log
  lines, never notifications.
- Failed check never renders green: a timed-out read, an
  `unknown` probe, a missing menu is AMBER/unknown in
  every surface (service-path-fleet-check fleet view,
  decision-board-lifecycle board) — never a
  green tick, never silently dropped.
- Notify transports (e-mail via `/tool/e-mail`, webhooks
  via `/tool/fetch`, push via the agent surface) are
  OUTSIDE this drill: prescribed, per-box configured,
  and each needs its own twin proof before the owner
  depends on it. Say which transport, show its test
  message, then trust it.

## Part 2 — Skill doc

### Trigger

Load when: setting up monitoring for a router or fleet;
adding or debugging a netwatch probe; choosing alert
thresholds; wiring a notification path; asking what healthy
looks like for a box; any "why didn't it alert?" postmortem.

### Prereqs

- centrs on PATH; target reachable (`first-contact` first
  on any box not yet in the device registry).
- A twin at matching firmware for probe-shape proofs.
- The look-after vocabulary: collect/investigate/notify
  cadences, hysteresis, dedup, announce-recovery,
  failed-never-green.

### Access

- Twins: anything goes; probe drills are cheap and safe.
- Production: reads free; ANY write asks the
  developer first — including netwatch adds (config
  writes + probe traffic).
- Operator Unknown → ask before any write.

### Envs

| Name | Use |
|---|---|
| `CENTRS_TIMEOUT` | Default 10s is ample for watch reads |
| `CENTRS_USERNAME` / `CENTRS_PASSWORD` | CLI fallback auth for `--host` targets |

### Outputs

- Read inventory: which watch-menus answer on this box.
- Probe record: host/interval/delay/scripts + the three
  transition log lines (down/up/recovery) with timestamps.
- Threshold record: alert value, clear value, dedup
  window, transport named + test message shown.
- Steady-state note: what silence means (all probes up,
  loop healthy) vs what unknown means.

### Verification

- `/tool/netwatch/print` shows expected states; no
  `unknown` past the startup-delay.
- `/log/print where message~"<marker>"` shows down, up,
  AND recovery lines for every probe shape shipped.
- Re-print after cleanup shows no leftover probes.
- Every owner-facing surface renders unknown as
  unknown — spot-check one amber path per surface.

### Recovery

- Probe stuck `unknown` → check `.about`: startup-delay
  still elapsing is normal; past the delay, the host/
  route is wrong. Never page on unknown.
- Scripts not firing → bodies must be single simple
  statements; check `:log` topics aren't filtered
  (`/system/logging/print`).
- Flapping alerts → widen hysteresis (alert/clear
  spread) or lengthen the dedup window; don't delete
  the probe.
- Log flooded → probe interval too short for the
  transport, or a real flap storm: read the states
  before touching the interval.

### Limits

- The scheduled loop is unbuilt: this skill
  proves probes, not the loop that reads them on a timer.
- Notify transports are prescribed, each needing its own
  twin proof (test message observed) before trust.
- Threshold scheduler mechanics are prescribed
  (routeros-scripting patterns, unexecuted here).
- CHR proves probe logic only: no sensors, no radios,
  no hardware failure modes. Hardware thresholds need
  hardware (or honest extrapolation, labeled as such).

Wersje

W bazie nie ma innych skilli o nazwie monitoring-alerting.

Migawka bazy z 13.11.2026 · wersja paczki 14e85bb605f0 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 96monitoring-and-alerting
    Pomaga konfigurować i diagnozować Prometheus, Grafanę, logowanie i system alertów.
  • 100creating-alerting-rules
    Tworzy reguły alertów dla proaktywnego monitoringu wydajności: progi, routing powiadomień i definicje monitorowania.
  • 100creating-alerting-rules
    Tworzy reguły alertów dla proaktywnego monitoringu wydajności: progi, routing powiadomień i definicje monitorowania.
  • 95ml4t-monitoring-alerting
    Buduje monitoring i alerty w czasie rzeczywistym dla systemów handlu na żywo, obejmujące potoki danych, dryf modeli i jakość wykonania zleceń.
  • 100monitoring
    Konfiguruje monitorowanie uptime, sondy zdrowia, alerty na spalanie budżetu SLO i rotację dyżurów dla działającej usługi.
  • 100prd-v08-monitoring-setup
    Definiuje strategię monitoringu, zbieranie metryk i progi alertów w PRD v0.8, w tym SLO, dashboardy i obserwowalność, z wpisami MON.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.