ModSyslogUI v1.0.2 [UPDATE] - add-on providing System Log page UI filtering capabilities

[kstamand]

This could lead to problems later on because the current update process downloads the new files, but then continues running the “old” script to do the install, instead of invoking the new scrip

Which is easily fixed @kstamand : just run

exec /path/to/script

after the update routine.

Thanks for the pointer, I didn’t know how to accomplish what @jksmurf was asking. Would using >> exec "$0" "$@" << after the update accomplish the same thing?

 

[thelonelycoder]

Thanks for the pointer, I didn’t know how to accomplish what @jksmurf was asking. Would using >> exec "$0" "$@" << after the update accomplish the same thing?

Yes, amtm does a similar thing, exec spawns a new shell.

 

[kstamand]

Just went in to amtm to check and it is indeed in the menu, so well done to you and thank you again! I really like the simplicity and it seems a few others (with scribe/uscribe) do too.

I did the update from the 'ms' menu there, but it still bugs me (as above, OCD much...?) that the version shows the same before and after you select update in the menu and does not change until after you exit the addon and and go back in again.

And now, a small equest... a number of addons have auto-update... no hurry but I like that feature ... and I cannot see it being a system-breaker here even if it does not go to plan.

v1.0.3 will properly display the version after an update, but I will wait a few days to see if there are any other simple update requests to include (I already have @maghuro update included).

Regarding auto-update, are you referring to from within amtm using the "u" option or something else? If from amtm, I believe the script has the proper setup for that already, but I welcome others feedback to help educate me further.

 

[thelonelycoder]

v1.0.3 will properly display the version after an update, but I will wait a few days to see if there are any other simple update requests to include (I already have @maghuro update included).

Regarding auto-update, are you referring to from within amtm using the "u" option or something else? If from amtm, I believe the script has the proper setup for that already, but I welcome others feedback to help educate me further.

amtm does not provide an auto-update feature as there is no common update logic for the various scripts it supports. Rather, some of the scripts themselves have such an option.

 

[visortgw]

amtm does not provide an auto-update feature as there is no common update logic for the various scripts it supports. Rather, some of the scripts themselves have such an option.

For example, one can enable the auto update function in MerlinAU.

 

[jksmurf]

For example, one can enable the auto update function in MerlinAU.

Also Tailmon.

 

[thelonelycoder]

amtm does not provide an auto-update feature as there is no common update logic for the various scripts it supports. Rather, some of the scripts themselves have such an option.

@kstamand wait with a script specific autoupdate function, I got something better cooking.

 

[kstamand]

@kstamand wait with a script specific autoupdate function, I got something better cooking.

Will do!!

 

[saison2023]

v1.0.1 (26-Jan-2026)
- Added: Supported firmware version check (3004.388.* and 3006.102.* only)
- Updated: Changed install completion verbiage, noting that editing logFilter.json is optional
- Added: Added a call to show the Menu at completion of install, instead of exiting the script
- Updated: Changed insert point for custom php code (UI filter option) so it will work with either 3004.388.* or 3006.102.*

Update to address code logic that adds the filtering option to the System Log page, allowing it to work with either firmware versions 3004.388.* or 3006.102.*.

Would appreciate if some with 3004.388.* firmware installed reply back here if it works and if not, provide any information that might help me debug.

Hello,
I installed your addon on my RT-AX86U running firmware 3004.388.11 without any issue.
I did some test and was able to filter the logs. I need to look deeper but it looks like very promising, great work!

May I suggest one thing: Could you update the original post?
You mentioned firmware 3006 and few router models but you didn't include/update this first post with v1.0.1 (26-Jan-2026) and 3004.388.* firmware support.
I had to read all pages and reached page #3 to see the v1.0.1's information.

Not really a big deal, just easier for the reader.

Again, great job, very interesting.

 

[Ripshod]

So, is this a good time to drop scribe? Will it work okay with a remote syslog server?

 

[kstamand]

Hello,
I installed your addon on my RT-AX86U running firmware 3004.388.11 without any issue.
I did some test and was able to filter the logs. I need to look deeper but it looks like very promising, great work!

May I suggest one thing: Could you update the original post?
You mentioned firmware 3006 and few router models but you didn't include/update this first post with v1.0.1 (26-Jan-2026) and 3004.388.* firmware support.
I had to read all pages and reached page #3 to see the v1.0.1's information.

Not really a big deal, just easier for the reader.

Again, great job, very interesting.

Thanks for the feedback and I have updated post #1

 

[kstamand]

So, is this a good time to drop scribe? Will it work okay with a remote syslog server?

Dropping scribe is a personal choice. Personally, (I'm biased / I know) I prefer the "lightweight" nature of this script and especially the updated capabilities I'm working on (teaser - presets support (add, delete, edit), enhanced help information (non-intrusive), and possibly expanded filtering expression support)