Notification Manager

Inspect notification settings, import/export them, and watch notifications emitted by the agent.

nimbus notification <command>

Command	Description
list	Show current notification settings (default command)
monitor	Stream notifications when agent-side rules emit them
export <path>	Export notification settings to a JSON file
import <path>	Import notification settings from a JSON file

Examples

# Show built-in and stream notification rules
nimbus notification list

# Watch emitted notifications
nimbus notification monitor

# Export/import settings
nimbus notification export /tmp/notification-settings.json
nimbus notification import /tmp/notification-settings.json

list prints built-in CPU/RAM/Disk rules and stream rules. monitor prints a line when a configured rule emits a notification, including its display label, source, field/value comparison, renotify interval, and custom message when configured. Built-in rules are displayed as CPU/RAM/Disk from GroupId, even when an explicit rule Name is present; Task Manager notification triggers still use the explicit name first and only fall back to the group label when the name is empty.

Recording and snapshot selections

Automatic rules use two independent alias lists with the same behavior as manual event reports. Set these fields on the notification rule in the exported JSON:

{
  "videoAliases": { "aliases": ["front-camera"] },
  "snapshotAliases": { "aliases": ["front-camera", "cloud-snapshot"] }
}

videoAliases links available video/CSV recordings. snapshotAliases selects video or enabled payload profiles: prepared images and supported triggering-message context are saved inside the event, while other payloads are separate resources. Internal image preparation shares one second and a 1 MiB combined internal-data limit. Selection and sample identity are frozen when the rule fires; capture failures produce explicit outcomes without suppressing the event. Saved occurrences retry when cloud connectivity returns. Resource uploads and links proceed independently.

Omitting either field preserves its existing list during an update. An explicit { "aliases": [] } clears that list. Aliases must be distinct within each list, with at most 16 entries across both lists; one alias may be used in both lists.

---