This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Zabbix, PRTG, and Nagios poll or receive traps in different habits. The builders draft an item key or a check command from names you type. The load calculator estimates polls. None of them installs the monitor. A check that logs into a device is a secret you do not put in the command text.
Write what you will poll, how often, and the device you administer. A default community in a sample command is deleted. One monitor is the later choice. This hour is the comparison.
Do not point a new poller at a device you do not run. prompt-for-this is not a community string.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- List the devices you would poll.
- Estimate the poll load.
- Draft one check and delete any secret.
- Pick a direction, not a deployment.
- Do not install a monitor.
- Stop.
Mistakes that outlive the command
Zabbix vs PRTG vs Nagios goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A community string in the check.
- A poller aimed at a foreign device.
- Installing during the reading.
- A one-second poll with no load estimate.
- Three products deployed to compare.
Decisions to write down
One decision for Zabbix vs PRTG vs Nagios: The devices are yours. The load was estimated. No secret is in the draft. Nothing was installed. And one direction is written.
Checks before you call it done
Confirm this before you call the change done: The device list is written. The interval is written. The load is written. No secret remains. And no monitor was installed. If one of those fails, stop.
| Habit | What you write |
|---|---|
| Poll | An interval and a load. A secret stays out of the item. |
| Trap or syslog | The device sends. You still name the collector. |
| A sample command | Delete the community string before the note is saved. |
Before you leave the device
Zabbix vs PRTG vs Nagios ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.