How to use notifiers in v4.0

[Future998]

In OpenUDS v4.0, there are notifiers, such as Telegram.

Tell me please how they should be used:

1. It is necessary to add the code in the places where notifications are needed?
2. This feature is needed for future versions?
3. Do they work for very rare events?

Because I have a problem:
INFO 2025-11-02 17:40:36,365 uds.core.managers.notifications:_ensure_local_db_exists 72 Cannot create local notifications table right now. Will try later.

Although at the same time:

sqlite> .tables
uds_notification
sqlite> .schema uds_notification
CREATE TABLE IF NOT EXISTS "uds_notification" ("id" integer NOT NULL PRIMARY KEY AUTOINCREMENT, "stamp" datetime NOT NULL, "group" varchar(128) NOT NULL, "identificator" varchar(128) NOT NULL, "level" integer unsigned NOT NULL CHECK ("level" >= 0), "message" text NOT NULL, "processed" bool NOT NULL);
CREATE INDEX "uds_notification_group_658c869c" ON "uds_notification" ("group");
CREATE INDEX "uds_notification_identificator_d4942d39" ON "uds_notification" ("identificator");

sqlite> SELECT * FROM uds_notification;
1|2025-11-02 17:12:45.878493|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1501 Field TelegramNotifier.check_delay not found in values data, |0
2|2025-11-02 17:12:45.948628|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/share/openuds/uds/core/module.py:156:__init__|0
3|2025-11-02 17:12:45.951753|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/share/openuds/uds/core/messaging/provider.py:79:__init__|0
4|2025-11-02 17:12:45.955078|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   <console>:1:<module>|0
5|2025-11-02 17:12:45.957378|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/lib64/python3.12/code.py:90:runcode|0
6|2025-11-02 17:12:45.959989|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/lib64/python3.12/code.py:74:runsource|0
7|2025-11-02 17:12:45.962240|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/lib64/python3.12/code.py:267:push|0
8|2025-11-02 17:12:45.964228|log|uds.log|40000|uds.core.ui.user_interface:__init__ 1504   /usr/lib64/python3.12/code.py:241:interact|0

[dkmstr]

https://deepwiki.com/search/can-you-explain-me-how-the-not_eb980560-ebf6-49db-aa77-5a8bc8bd9098?mode=fast

Can you take a look at that, and tell my is it is useful? :)

[Future998]

Yes, it's very useful, but it doesn't answer my questions.
I've already found out this information by studying the code, but this solution can speed up the process quite a bit.

[dkmstr]

Reading again your question, yes, it does not respond to it. Maybe these code lines helps a bit more:

openuds/server/src/uds/core/managers/notifications.py

Line 82 in 31325aa

def notify(

openuds/server/src/uds/core/messaging/processor.py

Line 75 in 31325aa

def run(self) -> None:

openuds/server/src/uds/core/util/log.py

Line 151 in 31325aa

def emit(self, record: logging.LogRecord) -> None:

But it is simple. There is a local DB (non important), to initially store all notifications. These are produced by the overrided logger, and with the process on background, is processed from time to time and released from local db. Why local db? to ensure that even if the remote db does not works, it still will be working.

[Future998]

Thank you so much for your help, it really made it clear, but what is the problem with my DB? Is it sensitive to migrations or does it need to be recreated after migration?

[dkmstr]

should not be.. anyway, you can simple remove the .db file and it will be recreated. What kind of error are you getting?

[Future998]

Yes, re-creating the database and a couple more simple steps really helped, thank you so much for your help.