Documentation

NRDEX Operations and Monitoring

Operational expectations for service continuity, observability, and support.

Operating model

NRDEX should be run as a continuously monitored national platform with clear accountability for availability, performance, and incident response.

Monitoring areas

  • Core platform uptime
  • Service latency
  • Failed requests
  • Certificate health
  • Queue or throughput pressure
  • Unusual access patterns

Logging requirements

  • Log service requests and responses at the required metadata level
  • Protect logs against unauthorized modification
  • Retain logs according to policy and legal requirements
  • Make logs available for audit and incident investigation

Incident response

  1. Detect and classify the event
  2. Contain affected services or access paths
  3. Notify relevant institutional stakeholders
  4. Recover service safely
  5. Record findings and corrective actions

Availability expectations

  • Define target uptime objectives
  • Schedule and publish maintenance windows
  • Test backup and recovery procedures
  • Review recurring failure patterns with participating institutions

Support model

Each participating institution should maintain both a business contact and a technical contact for production coordination, incident handling, and change notification.