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

[jksmurf]

Anyone out there who can confirm update v1.0.1 works as expected / doesn't have the problem @thelonelycoder reported in post #49 (namely, the System Log Page UI is not updated with the filtering options shown in post #1)?

Apart from the FW version, TBH I’m a bit confused about what was supposed to be missing, not working or not displayed in post #49 vs what is expected in post #1.

If you could clarify exactly what you expect to see and the steps to get there i can check it for you on my local system.

 

[Stephen Harrington]

@kstamand - really like the possibilities for this addon, thank you!

Is it on your roadmap to have presets/favourites in your GUI?
Something like 10 buttons (with user adjustable names) which give you instant access to your most-used filters?

 

[kstamand]

Apart from the FW version, TBH I’m a bit confused about what was supposed to be missing, not working or not displayed in post #49 vs what is expected in post #1.

If you could clarify exactly what you expect to see and the steps to get there i can check it for you on my local system.

Based on the file @thelonelycoder shared with me, I believe the text string I was using to insert the filtering code to be used on the System Log page doest not exist in the 3004.388 code base. And that led to the page not being updated properly and it messed with the log reading functionality overall.

This screenshot below is what I believe is what was missing for 3004.388 for this script and the v1.0.1 update uses a text string that is in both firmware versions and should fix the problem.

Does that help and better explain?

 

[jksmurf]

Does that help and better explain?

Yes, I guess you were saying an error was observed in the log filtering function for 3004.388 codebase Routers; which I do not have, so cannot see it .

 

[kstamand]

@kstamand - really like the possibilities for this addon, thank you!

Is it on your roadmap to have presets/favourites in your GUI?
Something like 10 buttons (with user adjustable names) which give you instant access to your most-used filters?

Actually yes, but probably not for a while yet. I need to gain a little more experience / confidence with asp coding before I'm ready to submit something with that level of functionality for community use.

Suggestions and pointers are welcome and thanks for the questions/input!!

 

[Stephen Harrington]

Actually yes, but probably not for a while yet. I need to gain a little more experience / confidence with asp coding before I'm ready to submit something with that level of functionality for community use.

Fair enough!
I currently run Scribe/uiScribe but your script with favourites/presets would be a much lighter weight alternative and give me most of what I need from time to time.
Will be watching with interest!

 

[kstamand]

Fair enough!
I currently run Scribe/uiScribe but your script with favourites/presets would be a much lighter weight alternative and give me most of what I need from time to time.
Will be watching with interest!

@Stephen Harrington - I see firmware version 3004.388 in signature. Did you happen to try my add-on and if yes, did the filter options show up on the System Log page as expected?

 

[JGrana]

Fair enough!
I currently run Scribe/uiScribe but your script with favourites/presets would be a much lighter weight alternative and give me most of what I need from time to time.
Will be watching with interest!

What would be log management Nirvana would be the merging of ModSyslogUI and ScribeUI. A way to quickly filter and view but also a method to save particular logs.

 

[Ellenswamy]

Uinstalled scribe and installed this on my BE98 Pro without issues. I will update if I see a problem but so far so good

 

[thelonelycoder]

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.

It might help if one actually could test it, but the script exits with "Firmware version 3004.388 not suppoted - exiting script", and I mean not the suppoted typo but the following really should equal to true for 3004.388:

case "$fwInstalledBranchVer" in
    "3004.388") SUPPORTED_FIRMWARE_VERSION=false ;;
    "3006.102") SUPPORTED_FIRMWARE_VERSION=true ;;
            *) SUPPORTED_FIRMWARE_VERSION=false
esac

Anyway, your script works now as expected on my RT AX86S with 3004.388 firmware.

 

[kstamand]

It might help if one actually could test it, but the script exits with "Firmware version 3004.388 not suppoted - exiting script", and I mean not the suppoted typo but the following really should equal to true for 3004.388:

case "$fwInstalledBranchVer" in
    "3004.388") SUPPORTED_FIRMWARE_VERSION=false ;;
    "3006.102") SUPPORTED_FIRMWARE_VERSION=true ;;
            *) SUPPORTED_FIRMWARE_VERSION=false
esac

Anyway, your script works now as expected on my RT AX86S with 3004.388 firmware.

Thanks for testing and getting back to me and the that setting has been corrected in the repo

 

[thelonelycoder]

Welcome to amtm @kstamand !

 

[kstamand]

v1.0.2 (31-Jan-2026) - Avoid duplicate or conflicting updates
- Update: Added code to check and remove potential duplicate custom mount points used by script
- Update: Added check to preserve user customizations to logFilter.json if / when Update function is run

During different testing scenarios with the "Install" and "Update" options, found that additional code checks were need to avoid duplicating mount points or javascript additions to the System Log page UI. This minor update corrects that situation.

Enjoy.

 

[maghuro]

Thanks for your work!
One thing I noticed, if I choose a non existent menu option (let's say 22), the script exits

 

[kstamand]

@maghuro - if you get the following screenshot error, that is by design.

Please describe what you were expecting or suggest be changed?

I'm assuming the preference is to return to the menu, which is a simple enough change. I was so focused on "functionality", that I missed simple UI behaviors like this.

I will easily / gladly make a v1.0.3 change to return to the menu in this type of scenario, after waiting a bit to collect any other feedback / suggestion changes.

THANKS for your input and please confirm that is what you were expecting (return to menu).

 

[maghuro]

@maghuro - if you get the following screenshot error, that is by design.

Please describe what you were expecting or suggest be changed?

I'm assuming the preference is to return to the menu, which is a simple enough change. I was so focused on "functionality", that I missed simple UI behaviors like this.

I will easily / gladly make a v1.0.3 change to return to the menu in this type of scenario, after waiting a bit to collect any other feedback / suggestion changes.

THANKS for your input and please confirm that is what you were expecting (return to menu).

View attachment 70159

Correct
Thank you for your answer!

 

[jksmurf]

Very minor: I selected (4) Update, it updated, but version still shows v1.0.0 in that main screen. Exit, go back in again, shows v1.0.1.

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.

 

[dave14305]

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 afetr you exit the addon and and go back in again.

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 script.

 

[jksmurf]

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 script.

I see; well outside my area of expertise, I am sure @kstamand will either take up teh baton and change teh way it does teh udpate, or decide it is not worth it to do it that way (which is OK, it is his preference). Just the experience from other addons that do it the way I personally prefer.

 

[thelonelycoder]

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 script.

Which is easily fixed @kstamand : just run

exec /path/to/script

after the update routine.