Skip to main content

Logging and Alerting

Reviewed on: 2026-01-21 Status: Draft (requires deployment-specific configuration)

This document defines baseline logging and alerting expectations for Primus deployments.

Logging​

  • Enable structured logging for application and security events.
  • Enable PII masking before logs leave the service boundary.
  • Forward logs to a centralized sink (AppInsights, ELK, Datadog, etc.).

Alerting​

  • Alert on authentication failures, webhook signature failures, and policy engine blocks.
  • Alert on spikes in security findings or error rates.
  • Alert on high latency or queue backlogs (notifications, webhooks).

Evidence Needed for Production​

  • Log sink configuration and retention policy.
  • Alert rules and paging policies.
  • Dashboard or monitoring snapshots.

Review Log​

  • 2026-01-21: Baseline guidance documented. Configuration pending.