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

[kstamand]

modsyslogui/customlogic.js at 71e1ca7b7ba48b8808a06b96e49c3089a6fa8ccd · kstamand/modsyslogui

Modify Asuswrt-Merling System Log page with filtering capabilities - kstamand/modsyslogui

github.com

|AND OR| ????

Corrected - thanks for the catch

 

[kstamand]

Let me put your mind to rest, I have your script on radar.

Checking back to see if this script is still on the radar or if there is something I need to do for this to be included in AMTM support?

 

[ExtremeFiretop]

Checking back to see if this script is still on the radar or if there is something I need to do for this to be included in AMTM support?

I don't want to speak for @thelonelycoder but I do know he has a set of basic requirements for an addon to considered for integration into AMTM.

I'll link you to these requirements below so you can see if your add-on meets them:
Post in thread 'Utilize the robot to assist in analyzing router logs.' https://www.snbforums.com/threads/u...st-in-analyzing-router-logs.89410/post-899903

Hope this helps.

 

[jksmurf]

I'll link you to these requirements below so you can see if your add-on meets them:

- Must be popular on SNB

I wonder how they measure that...

 

[ExtremeFiretop]

I wonder how they measure that...

Again I don't want to speak for thelonelycoder, so please just take this as my opinions only.

The easiest way that I know of is views on the thread.
Currently this thread has about 2,000 views.

You can also use the amount of replies on the thread.
Which this thread has 43 replies (44 when I hit submit)

Another method, although less direct, is stars on GitHub.
Which this project is at zero so far, stars on Github is not so related to SNB so it's less likely he's using that, but stars does show a good indication that people are trying to find/pin the project.

I'm sure the mods of these forums have additional tools, since XenForo is extremely good behind the scenes at tracking everything.

 

[jksmurf]

Again I don't want to speak for thelonelycoder, so please just take this as my opinions only.

okey dokey, ta

 

[kstamand]

I don't want to speak for @thelonelycoder but I do know he has a set of basic requirements for an addon to considered for integration into AMTM.

I'll link you to these requirements below so you can see if your add-on meets them:
Post in thread 'Utilize the robot to assist in analyzing router logs.' https://www.snbforums.com/threads/u...st-in-analyzing-router-logs.89410/post-899903

Hope this helps.

Thanks for that info, much appreciated!!

 

[Ravenbak]

hi,
So after updating to new alpha build 3006.102.7
nothing is showing in log and i have dupliated modsyslog

 

[thelonelycoder]

Checking back to see if this script is still on the radar or if there is something I need to do for this to be included in AMTM support?

This script is limited to routers running 3006.102.* firmware. It does no checks if it is compatible on a router, just installs it, with frustrating outcome.
I would appreciate if at least the 3004.388 branch is still supported.

Also, after the installation the script returns to the shell prompt instead of showing the ModSysloUI when it clearly prompts to:

ModSysloUI installation complete!
- be sure to run the ModSyslogUI EDIT command (menu option #5), to modify the logFilter.json to exclude System Log records to your likings

 

[kstamand]

This script is limited to routers running 3006.102.* firmware. It does no checks if it is compatible on a router, just installs it, with frustrating outcome.
I would appreciate if at least the 3004.388 branch is still supported.

Also, after the installation the script returns to the shell prompt instead of showing the ModSysloUI when it clearly prompts to:

ModSysloUI installation complete!
- be sure to run the ModSyslogUI EDIT command (menu option #5), to modify the logFilter.json to exclude System Log records to your likings

Thanks for the feedback.

I don’t have another router to test with 3004.388, but it would be helpful to know what the frustrating outcome was so I can check into it.

 

[thelonelycoder]

I don’t have another router to test with 3004.388, but it would be helpful to know what the frustrating outcome was so I can check into it.

The modifications are not applied to the asp file, hence no changes are seen on that page in the WebUI.
I pasted the content of Main_LogStatus_Content.asp to pastebin from my RT-AX86S with FW 3004.388.11
You'll figure it out, I'm sure.

 

[kstamand]

The modifications are not applied to the asp file, hence no changes are seen on that page in the WebUI.
I pasted the content of Main_LogStatus_Content.asp to pastebin from my RT-AX86S with FW 3004.388.11
You'll figure it out, I'm sure.

Thank you kindly!

 

[kstamand]

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.

 

[jksmurf]

v1.0.1 (26-Jan-2026)

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.

 

[kstamand]

hi,
So after updating to new alpha build 3006.102.7
nothing is showing in log and i have dupliated modsyslog

Thanks for providing this info. Unfortunately I haven't tested with the 3006.102.7 alpha build and probably won't test the script against it until the Beta build is out.

I will reply back to this thread with any updates if needed tho, so stay tuned.

 

[dave14305]

Unfortunately I haven't tested with the 3006.102.7 alpha build and probably won't test the script against it until the Beta build is out.

None of the Web UI changed in the alpha, so it’s probably not specific to the alpha. How do you prevent Mod_Syslog_Asp() from running more than once? Do you check if the mod was already applied before applying it?

 

[kstamand]

@Ravenbak - I don't want to assume, but what does "have duplicated modsyslog" mean >> does it mean 2 copies of the modsyslogui script in the /jffs/addons/modsyslogui directory?

@dave14305 - thanks for the questions, they have me rethinking the install () and update () functions to avoid duplicating updates in Mod_Syslog_Asp() and/or not applying the latest updates.

Once I hear back from @Ravenbak, and if the v1.0.1 update works on 3004.388, I will work in pushing out a v1.0.2 update

 

[Ravenbak]

@Ravenbak - I don't want to assume, but what does "have duplicated modsyslog" mean >> does it mean 2 copies of the modsyslogui script in the /jffs/addons/modsyslogui directory?

@dave14305 - thanks for the questions, they have me rethinking the install () and update () functions to avoid duplicating updates in Mod_Syslog_Asp() and/or not applying the latest updates.

Once I hear back from @Ravenbak, and if the v1.0.1 update works on 3004.388, I will work in pushing out a v1.0.2 update

@kstamand I already update to v1.0.1 and it's working fine on 3006.102.7 alpha1

 

[jksmurf]

I already update to v1.0.1 and is working fine with 3006.102.7 alpha1

Can second this. My update above was on 3006.102.7 alpha1.

 

[kstamand]

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)?