CIRCUITO
CARIOCA TI · DOCUMENTATION
♙
Nagios Core · Observability

Performance Data and Time Series

Separe estado de check de métricas de performance e encaminhe perfdata para backend apropriado.

nagios://performance-data
$ baseline: 4.5.14
$ topic: Performance Data and Time Series
$ validation: step-by-step
$ method: evidence-first_
01 · Scope

Performance Data and Time Series

Separe estado de check de métricas de performance e encaminhe perfdata para backend apropriado.

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

process_performance_dataValidate this point in design, implementation, and troubleshooting.
service_perfdataValidate this point in design, implementation, and troubleshooting.
latencyValidate this point in design, implementation, and troubleshooting.
execution timeValidate this point in design, implementation, and troubleshooting.
external TSDBValidate 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.
# Valide primeiro em laboratório
# Registre estado inicial, mudança, resultado e rollback
# Nunca aplique alteração em produção sem uma verificação pós-mudança
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.