pnclPULSEGet API access

DROP ALERT NOTES

Inheriting a drop alert setup: audit before you change it

Someone else's thresholds and rules come with no explanation. Read them from the log first, change them second: the three-step audit for a handover.

You took over a drop alert relay: someone else's min_drop, someone else's channels, a rule table with no comments. The temptation is to fix it immediately. Resist. The setup encodes decisions that made sense to someone, and the way to learn which ones still make sense is an audit, not an edit. Three steps, all reversible, before you change a number.

Step one: read the rules as data

Extract the current state: the connection's min_drop, the filter rules, the cooldowns, the routing table and the channels each rule feeds. Write them down in one document, because a setup you cannot describe is a setup you cannot audit. The drop alerts guide lists what a threshold and a window actually mean, so you can translate their numbers into intent, checked 2026-10-20.

Every number you cannot explain goes on the audit list. Most setups have several.

Step two: run the log, not the editor

Before changing anything, replay two weeks of alerts through the existing rules and read the decision record: what passed, what was filtered, what was deduped, what actually got acted on. The dedupe guide's own measure-the-effect posture applies: the setup's behavior is visible in its log, and the log is the only honest description of what the rules do in practice.

The questions that matter: which rules never fire a decision, which channels are read, and which alerts the previous owner acted on manually despite the rules.

Step three: change one thing, and only one

Pick the single worst finding from the audit and fix that alone, with the change date logged. Everything else stays for another month, because a setup changed in five places at once is a setup you can no longer attribute results to. The change-log discipline from the threshold guides applies: every change is dated, so next month's comparison has a boundary.

If the audit says the setup works, the correct change is none, and the document you wrote is the handover gift for the next person.

Read the rules, read the log, change one thing. An inherited setup is a hypothesis about someone else's alerts, and the audit is how you find out whether it is true.