Mimir

← Back to documents

Issue: Investigate Notification Service operational risk 17

github
notification
bcf4dd3cb6c3

github/issue-gh-5017-notification.md

Issue: Investigate Notification Service operational risk 17

ID: GH-5017 Date: 2026-01-14 Repository: acme-commerce/notification-service Service: Notification Service Owner: Engagement Platform Status: open Type: issue

Summary

This issue tracks production-readiness work for the Notification Service. The concern is related to schema drift between a downstream contract and the deployed parser. The implementation area touches API contracts API-NOTIFICATION-01, API-NOTIFICATION-02, service telemetry, and operational runbooks.

Engineering Notes

  • Validate that retries are bounded and idempotency keys are respected.
  • Add structured logs with service, correlation_id, and customer_impact fields.
  • Confirm dashboards show p95 latency, error rate, dependency saturation, and queue depth.
  • Cross-service impact should be reviewed with Checkout Service, Billing Service, Inventory Service, Authentication Service, and Notification Service owners when applicable.

Acceptance Criteria

  1. Contract tests cover expected and malformed payloads.
  2. Runbook references are updated for Notification Service.
  3. The change can be linked from Jira remediation tickets and incident reviews.