CIRCUITO
CARIOCA TI · DOCUMENTATION
♙
Nagios Core · Agents

NRPE and Remote Checks

Use NRPE com escopo mínimo, TLS e comandos permitidos explicitamente; evite argumentos remotos irrestritos.

nagios://nrpe-remoto
$ baseline: 4.5.14
$ topic: NRPE and Remote Checks
$ validation: step-by-step
$ method: evidence-first_
01 · Scope

NRPE and Remote Checks

Use NRPE com escopo mínimo, TLS e comandos permitidos explicitamente; evite argumentos remotos irrestritos.

This module follows an evidence-first workflow: isolate collection, processing, storage, state evaluation, and presentation before changing production settings.

check_nrpeValidate this point in design, implementation, and troubleshooting.
allowed_hostsValidate this point in design, implementation, and troubleshooting.
dont_blame_nrpeValidate this point in design, implementation, and troubleshooting.
TLSValidate this point in design, implementation, and troubleshooting.
local pluginsValidate this point in design, implementation, and troubleshooting.
02 · Procedure

Production-safe workflow

  1. Define the operational objective and expected result.
  2. Record version, topology, dependencies, and required flows.
  3. Test the underlying protocol or plugin outside the monitoring scheduler.
  4. Validate configuration before reload/restart when the platform supports it.
  5. Apply the smallest change and watch logs plus one full collection cycle.
  6. Keep a tested rollback path.
sudo systemctl status nagios-nrpe-server
/usr/lib/nagios/plugins/check_nrpe -H 192.0.2.20 -c check_disk
03 · Validation

Acceptance criteria

  • Main process is healthy and logs show no recurring error.
  • Manual collection returns the expected value.
  • Scheduled collection finishes within its time budget.
  • Frontend timestamps and states match the source.
  • A controlled failure and recovery produce the expected lifecycle.
04 · Security

Management-plane security

Monitoring systems expose topology, inventory, versions, credentials, and operational state. Apply segmentation, least privilege, secure protocols, protected secrets, and explicit administrative access controls.

05 · References

Validated sources

Editorial review

The English version preserves structure and critical technical guidance. A final deep language-equivalence review remains scheduled for the end of the Systems migration.