Notification System

Rust-Srec records notification events and can deliver selected events to external channels. Channel delivery is configured independently from the interface language and from browser-only notifications.

Available Destinations

Destination	v0.5 web interface	Requirements
Webhook	Create, edit, test	HTTPS endpoint; optional headers or auth
Telegram	Create, edit, test	Bot token and chat ID
Gotify	Create, edit, test	Server URL and application token
Email	Create, edit, test	SMTP host, sender, recipients; credentials optional only when the relay permits it
Discord	Existing channels can be represented; new selection is disabled in the v0.5 form	Backend/API supports Discord webhook settings
Web Push	Configure per browser	VAPID keys and HTTPS, or localhost
Live polling	Configure per browser	The application tab must remain open
Desktop notification	Desktop build only	Operating-system notification permission

Discord is therefore a backend capability with a web-interface limitation, not a generally selectable v0.5 UI channel.

Configure an External Channel

1. Open Notifications and select Add Channel.
2. Choose Webhook, Telegram, Gotify, or Email and enter a recognizable channel name.
3. Set Minimum Priority, message language, and Enabled.
4. Save the channel, then use its test action. A saved channel is not proven until the receiver gets the test.
5. Open the subscription manager and select the event types that should be sent to that channel.

Channel settings and subscriptions are separate. Creating a destination without subscribing it to events does not make it receive every event automatically.

Priority

Priorities use a 0-10 numeric scale in the API and UI settings:

Level	Value	Examples
Low	2	Stream offline, segment progress, pipeline start/completion
Normal	5	Stream online, download completion, system startup/shutdown
High	8	Download error/rejection, pipeline failure, credential refresh failure, Baidu Netdisk re-login failure
Critical	10	Fatal error, output path inaccessible, out of space, invalid credential

A channel filters events below its minimum. The API also accepts the legacy labels low, normal, high, and critical where documented; info is not a valid priority.

Language

Each external channel can follow the server language or override it with en or zh-CN. RUST_SREC_LOCALE sets the default for backend-rendered messages. This is independent of the language selected by a user in the web interface.

Web Push

Generate a VAPID key pair and set all three variables before starting the backend:

docker run --rm ghcr.io/hua0512/rust-srec-vapid:v0.5.1

WEB_PUSH_VAPID_PUBLIC_KEY=...
WEB_PUSH_VAPID_PRIVATE_KEY=...
WEB_PUSH_VAPID_SUBJECT=mailto:operations@example.com

Then open Notifications, enable Web Push for the current browser, grant browser permission, choose priority, and send a test. Browsers require a secure context; use HTTPS outside localhost.

Delivery Behavior

External channel delivery retries transient failures with backoff and uses a circuit breaker for repeatedly failing channels. Exhausted deliveries are dead-lettered and notification events remain available in the event history according to the configured retention period.

These mechanisms reduce transient loss but do not create an end-to-end delivery guarantee. Monitor the receiving service, use the channel test after configuration changes, and configure a second destination for critical events.

Critical Storage Events

• out_of_space indicates that the disk threshold has been crossed.
• output_path_inaccessible means the output-root write gate has blocked new recording work because a tracked root cannot be written.

Freeing genuine disk exhaustion can recover automatically after the next probe. A stale Docker bind mount may require a container restart; see Storage and Capacity.