How do I configure notifications and pause server reminders?

Choose when a server counts as forgotten

1. Right-click Radar's icon, choose Settings…, and open Alerts.
2. Turn on Notify when a server has been running a long time.
3. Set Consider a server forgotten after to 2 hours, 4 hours, 8 hours, 12 hours, or 24 hours.

The rule starts enabled at 8 hours. Its picker is disabled when the rule is off. Changes save immediately and are evaluated on a later successful scan.

Radar compares the current time with the server group's root start time. “Forgotten” is an age threshold, not a judgment about whether you are still using the server. A Background badge is not required. An already-old server can alert soon after Radar begins monitoring it.

Long-running reminders repeat at each multiple of the selected threshold while the server remains eligible. With 2 hours, a server can remind at 2, 4, 6 hours, and so on. With 8 hours, repeats occur at 8, 16, 24 hours. Remind again every belongs to the memory rule and does not change these age multiples.

Turn the long-running switch off to disable the rule globally. Use Stop reminding on one long-running notification to silence that kind for the particular server, or use a project snooze to pause both kinds temporarily.

Choose a memory limit and reminder interval

1. In Settings… → Alerts, turn on Notify when a server uses too much memory.
2. Choose Memory threshold: 512 MB, 1 GB, 2 GB, 4 GB, or 8 GB.
3. Choose Remind again every: 15 minutes, 30 minutes, 1 hour, or 2 hours.

Memory notifications are off initially. The first time you enable them with no saved threshold, Radar sets 2 GB. The default repeat interval is 30 minutes. Both pickers are disabled while the memory switch is off. Turning it off retains its saved threshold and interval for later use.

The threshold applies to one server card's combined process memory, not the panel's total. It uses 1,048,576 bytes per MB and fires when the sampled memory is strictly above the chosen threshold. It first alerts when Radar observes the excess, then repeats at the chosen interval while the group stays above it.

For example, with 1 GB and 30 minutes, the first sampled excess produces a notification. If memory stays above the limit, reminders follow at 30 and 60 minutes after that observed excess. If a sample drops to or below the threshold, a later excess starts a new episode and can alert again. Scan timing means these are observed events, not continuous measurement.

No CPU notification rule is available. Orange CPU text on a card is a visual cue only.

Allow notifications and choose how they appear

Radar requests macOS notification permission when it first has an alert to post, rather than at app launch. Allow it if you want notifications. Permission denial prevents delivery even when the Radar rule is enabled.

1. In Settings… → Alerts, find Keep alerts on screen until dismissed.
2. Click Open Notification Settings….
3. In macOS's Radar Dev Monitor notification settings, allow notifications and choose the Alerts style if you want them to stay until dismissed.

Radar opens the app-specific notification settings link; macOS controls the available presentation choices. Radar also requests permission for sound, but its current notification content does not specify a sound. Do not rely on an audible warning.

Clicking a notification's body opens the Radar panel. It does not open a specific Details window or automatically stop a server. Radar requests banner and Notification Center presentation while it is active too, but final delivery and appearance remain controlled by macOS.

Use an alert without silencing every rule

Both kinds of notification offer these actions when macOS exposes their controls:

Stop reminding on a long-running warning leaves memory alerts active. On a memory warning, it leaves long-running alerts active. The card displays Long-running reminders off or Memory reminders off so you can see which choice is in effect.

These silences are temporary and kept in Radar's current monitoring session. They clear when the server is restarted or leaves the alert-evaluated set, and when Radar itself is relaunched. They are not saved project preferences. To undo them sooner, open that server's Details and click Resume alerts.

Radar removes delivered warnings when the server leaves its visible monitored list. Stop reminding removes already-delivered warnings of that kind for the server. Quitting Radar removes all its delivered warnings. Dismissing a banner is not the same as turning off a rule; use the explicit action or setting for that.

Pause all alerts for a project for one hour

1. Open a server's Details… window.
2. Under Project preferences, click Snooze alerts for 1 hour.
3. Check the Until [time] text.
4. Click Resume alerts to end the snooze early.

Snooze pauses age and memory alert evaluation for every card using that project folder. It leaves the cards visible and does not stop servers or readiness checks. The end time is saved, so reopening Radar does not start a new hour. Clicking Snooze again sets the end time one hour from that click.

After the end time, eligible servers are evaluated again on a successful scan. A server already above an age or memory threshold can warn then. Snooze is not a promise to wait for a fresh threshold crossing after the hour ends.

Resume alerts clears the shared project's snooze and also clears both temporary reminder silences for the particular server whose Details is open. It does not directly clear per-server silences on every other card. Ignoring a project is a separate way to remove it from the monitored set entirely.

Check why a warning did not arrive

1. Check the correct rule is on in Alerts. For memory, check both the threshold and repeat interval. Long-running repeats use the age threshold instead.
2. Confirm the server is visible in the panel. Disabled detection and ignored projects can remove it from alert evaluation.
3. Open Details and check for an active Until [time] snooze. Use Resume alerts if you want evaluation now.
4. Check the card for Long-running reminders off or Memory reminders off, then Resume alerts for that server if needed.
5. Check notification permission and presentation with Open Notification Settings….
6. Check the header's last sample and any scan warning. Radar evaluates on successful scans and pauses during sleep.

A long-running reminder is sent once per new threshold multiple, not on every scan. Memory must be above the threshold for that server group, not just equal to it or high across all servers combined. A denied first notification is not replayed immediately just because you later allow permission; a later repeat or renewed eligible episode may be needed.

If you recently changed a threshold, toggled a rule, snoozed, ignored, or resumed a project, note that sequence in a support report. Those changes can reset or retain parts of the current alert episode. Do not keep toggling settings simply to test notification delivery; first check the saved options and macOS permission.