Preparing your design workspace

Loading the problem and your saved attempt…

Design a Threshold Logging and Alerting Model

Write file logs at INFO, WARNING, or CRITICAL, notify subscribers when a configured threshold is crossed, and let them subscribe or unsubscribe.

Design an in-process logging and alerting object model.

For this exercise, assume a CRITICAL log increments a counter and, when the count first reaches the configured threshold, each subscriber is notified through their selected channel. For this exercise, assume users can subscribe or unsubscribe from an alert type without restarting the logger.

For this exercise, assume logs are written to a file and have INFO, WARNING, and CRITICAL types. For this exercise, assume log shipping, dashboards, and on-call paging policies are out of scope.

For this exercise, assume a concrete walkthrough writes three CRITICAL logs against a threshold of two and notifies the current subscribers. For this exercise, assume a focused follow-up will ask how a new notification type is added without rewriting the logger.

For this exercise, define threshold crossing as moving from below the threshold to at or above it; a threshold of two is first reached by the second CRITICAL log. State whether later logs retrigger alerts or whether the policy stays latched until reset.