SYNC Notifications Spam

[adamoutler]

I enabled sync between nodes. Every minute, an INFO log was generated. This is an extreme amount of log spam per day for notifications.

I thought about how to fix it, and the answer is: There's no way this should be a notification at INFO level as there are 1440 notifications generated per day. I located the line in the code:

            message = f'[{pluginName}] Device data from node "{node_name}" written to {log_file_name}'
            mylog('verbose', [message])
            write_notification(message, 'info', timeNowTZ())

I then updated from info to verbose, but this made the problem worse, now the notifications show red tags instead of green in verbose mode:

The same color is assigned to debug level.

I had considered submitting a PR to remove the problematic line, but maybe there's a use case for 1440 notifications per day? Maybe there's a way to filter out SYNC notifications?

[jokob-sk]

Hi @adamoutler ,

I just pushed a fix - if you set your LOG_LEVEL setting to minimal these should disappear. The change will be live in the netalertx-dev image in about 15 min.

Thanks for all the feedback and PRs - much appreciated.

[Rikysonic]

Hello, I've changed LOG_LEVEL to "minimal" and the notifications disappear as expected, thank you!
Could it be possible to apply the same fix to "[Plugin: SYNC] Data sent" so that notifications disappear from nodes too?

[jokob-sk]

This should be available/fixed in the next release.
It would be great if you could test the ghcr.io/netalertx/netalertx-dev-unsafe Docker image in ~15 minutes (or once the latest GitHub Action finishes).

⚠️ Please back up everything first, or ideally spin up a separate container with its own DB and config (a copy of your current setup), as database changes may occur.

After updating:

• Click the 🔄 refresh button in the blue header at the top
• Hard refresh your browser cache (shift + reload) to force js and css files reload

👉 If I don’t receive confirmation that this works, I may temporarily remove the feature to avoid introducing bugs.

If you find NetAlertX useful, consider sharing the app on forums or socials, at your work, or share a quick review on Reddit or elsewhere to help support the project. See more ideas and how-to in the growth playbook.

Disclaimer: Running the dev container long-term may lead to data loss, as upgrade paths are not guaranteed.

Thanks in advance,
j

[jokob-sk]

@Rikysonic can you please test? Otherwise I'm rolling this back in the next few days.

[Rikysonic]

Hello, I've just tested latest dev-unsafe, I can confirm the notification "[Plugin: SYNC] Data sent" on nodes disappeared, thanks!

[jokob-sk]

great, thanks for testing

[adamoutler]

These notifications should probably be lowered to verbose or debug. The app logs work fine for identifying when a sync took place. I don't think it's necessary to have such verbose information at an info level. Info is usually reserved for things people might like to know... Eg.

• Device is offline for 24 hours.
• The internet IP changed
• Two devices with the same IP are detected

Debug would be for things like

• A new device was inserted with properties...
• Other developer optiobs

I think a once-per-minute sync falls directly within verbose and possibly debug level of logging. The updates occur within the system and are broader than most plugins which makes it more important. At the same time, the frequency spams the logs making the inserts of devices and changing of configuration fall down to the 10th page in a day, greatly increasing the search time required.

[jokob-sk]

Hi,

Thanks for the feedback!

Have you tried to switch LOG_LEVEL setting to minimal on the netalertx-dev container? That should mute these completely.

The once per minute frequency is due to the frequency of the plugin execution.

Also just FYI when it comes to actual email or push alerts the control is more granular:

https://jokob-sk.github.io/NetAlertX/NOTIFICATIONS/?h=not

For the in app notifications there are only 3 levels, info, alert, interrupt.