The Nagios ecosystem
The whole ecosystem, not just the install: Core, XI, Log Server, Network Analyzer and Fusion.
Protocols and monitoring fundamentals
The module the course opens with, and the one most often missing elsewhere. Before configuring a check you need to understand what you are asking and at which layer. We walk almost the full OSI model — see the table below — and practise with packet capture to see, live, what a device answers when Nagios asks.
Nagios Core — the engine
Internal architecture, the check execution cycle, configuration files, templates and inheritance, macros and environment variables. Understanding Core is what lets you debug XI when the interface is not enough.
Nagios XI — daily operation
Configuration wizards, users and permissions, dashboards by business area, availability and SLA reporting, the REST API, and the relationship between what the interface does and what it writes into Core.
Active checks, passive checks and agents
NRPE, NCPA and NSClient++ for agent-based checks; NSCA and SNMP traps for passive ones. When each fits, and why passive monitoring stops being optional in large environments.
Thresholds, dependencies and noise
How to set thresholds that do not produce useless alerts, how to model host and service dependencies so a single root failure does not fire hundreds of derived alerts, and how to revisit all of it as the estate grows.
Nagios Log Server
Centralizing syslog and Windows Event Log, indices and retention, search and correlation, alerting from the log, and its integration with XI.
Nagios Network Analyzer
NetFlow, sFlow, J-Flow and IPFIX: what each device exports, how it is collected, and how to read link consumption at flow level — the view XI checks do not give on their own.
Nagios Fusion
Aggregating several XI instances into a single view, for operations spread across sites or business units.
Plugins and Nagios Exchange
The bundled plugins, the community library, and how to write your own so it behaves: exit codes, performance data and timeouts.
Sizing and tuning
How much hardware an environment needs given hosts, services and check frequency; when distributing with workers becomes necessary; and how the platform behaves going from one thousand to ten thousand services.
