Notifications

Where to find it?

On the home page, click the Notifications icon in the top bar. The section is available to an authorized User if the instance has PU_FF_NOTIFICATION_ENABLE on

WARNING

The list contains only your notifications

Filters and table

The All, Unread, and Read buttons leave all records, only unread ones, or only read ones. The Types button turns types on and off one by one.

Column	What it shows
Type	Notification type
Text	Short line. Hover shows the table. The icon opens the full log if there is one
Created	Creation time
Status	Read, or a Mark read button

Mark all read marks all of your unread records as read.

Settings

Settings are in the menu of your own name, the Notification Settings button. The settings row is created together with the account.

Toggle	Default	What it does
Daily summaries	on	Creates daily summaries of the instance and Units
HH:MM UTC	16:00	Summary time, 00:00–23:59 UTC
Data pipe alerts	on	Live page updates for DataPipe alerts. A Telegram message is sent when Telegram delivery is on and a chat is linked. The record in the list and the rule in the pipeline stay
Telegram delivery	on	Messages in the Telegram Bot. The list and live page updates stay. The button is present when PU_FF_TELEGRAM_BOT_ENABLE is on

Manual command results always arrive: integration tests, Instance polling, RepositoryRegistry updates, and Unit firmware updates.

Delivery

A live update of the open page goes to any User who is not blocked, when the setting for that type is on. A Telegram message is sent when the user has a linked chat and Telegram delivery is on. A summary is created when Daily summaries is on. A DataPipe alert always lands in the list, reaches the page when Data pipe alerts is on, and reaches the chat when Telegram delivery is also on and a chat is linked.

In the Telegram Bot, the /alerts command opens your notifications. The short text goes to the chat, a press shows the table, and integration tests have a full-log button. There is a pause between messages to one chat, and the whole instance has a shared rate limit. The numbers are set by Backend variables.

Types

Type	Kind	Who	Description
InstanceDailyState	Periodic	Administrator	Up to 3 groups of ERROR and CRITICAL from Backend logs for the day. The source is Loki
UnitDailySummary	Periodic	User with their own Units	Up to 10 of their own Units with the largest number of Error and Critical logs for the day
DataPipeAlert	DataPipe	Creator of the Unit	A UnitNode value violated the alerts block. The line has the Unit name, the value, and the check; the table also has the topic. How to set the rule
IntegrationTests	Operation	Administrator	Backend integration tests. The full log is the pytest output. Learn more
ScanAllInstances	Operation	Administrator	Poll of all trusted external Instances. The button is present when PU_FF_FEDERATION_ENABLE is on. Repeat after 10 minutes. Result Scanned N, failed M
ScanInstance	Operation	Administrator	Poll of one trusted external Instance
UpdateAllRegistries	Operation	Administrator	Sync of local copies of every RepositoryRegistry
UpdateRegistry	Operation	User with access to the registry	Sync of the local copy of one RepositoryRegistry
UpdateUnitsFirmware	Operation	Creator of the Repo	Firmware update of Units of this Repo that have auto-update on
UpdateAllUnitsFirmware	Operation	Administrator	Firmware update of every Unit that allowed auto-update from a Repo with Auto-update on

• Periodic ones are created once a day, at the minute from HH:MM UTC, for a User with Daily summaries on. A blocked user does not get a summary.
• An operation leaves two records: Running at start and Success or Error after it finishes. The table has the status, start time, end time, and a short result line.