Plugins and Plugin API

Entenda contrato de exit codes, stdout e performance data; teste plugins no shell antes de delegar ao Core.

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

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.

/usr/lib/nagios/plugins/check_http -H example.net -S -w 1 -c 3
echo $?

• 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.

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

• Nagios Core releases
• Nagios Core documentation
• Nagios Plugins
• CERT.br security practices