uiScribe uiScribe - Custom System Log page for "scribed" logs

[Jack Yaz]

Expand log shouldn't be there, that's for debugging syslog-ng issues is it not?

 

[joe scian]

Expand log shouldn't be there, that's for debugging syslog-ng issues is it not?

Thanks removed that filter - reinstalled uiScribe - all working perfectly now

 

[Jack Yaz]

Thanks removed that filter - reinstalled uiScribe - all working perfectly now

Glad that sorted it. I'll fix that in the next version (i.e. Exclude it from the UI list)

 

[no_name]

Scribe is gobbledygook for me at the moment so I’ve sat back and followed the thread with a lot of interest and learning a little more as your uiScribe script progresses and the input from the people who do understand

I have now installed Scribe and uiScribe

Thank you for turning a subject I don’t really understand into a product a complete novice like myself can understand [emoji106]




Sent from my iPad using Tapatalk

 

[Jack Yaz]

Scribe is gobbledygook for me at the moment so I’ve sat back and followed the thread with a lot of interest and learning a little more as your uiScribe script progresses and the input from the people who do understand

I have now installed Scribe and uiScribe

Thank you for turning a subject I don’t really understand into a product a complete novice like myself can understand [emoji106]




Sent from my iPad using Tapatalk

Scribe is doing the heavy lifting to get syslog-ng installed and configured so easily, all I'm doing is loading that into some textareas!

 

[no_name]

Scribe is doing the heavy lifting to get syslog-ng installed and configured so easily, all I'm doing is loading that into some textareas!

Thank you for pointing that out, my thanks also goes to cmkelley and his script for doing the heavy lifting [emoji4]


Sent from my iPad using Tapatalk

 

[cmkelley]

Glad that sorted it. I'll fix that in the next version (i.e. Exclude it from the UI list)

That said, it should have processed it like any other file and listed '/opt/var/log/expanded-syslog.log' instead of 'file("/opt/var/log/expanded-syslog.log" template(t_expandlog));' It's not unreasonable to expect someone may use a template or other modifier to the file statement.

I've no heartburn with excluding it though ... it gets big really quick and as you noted it really is for debugging.

 

[cmkelley]

Scribe is doing the heavy lifting to get syslog-ng installed and configured so easily, all I'm doing is loading that into some textareas!

Thanks for the vote of confidence. I guess it all depends on what we consider easy. To me, getting it into the webui is magic incantations.

 

[Jack Yaz]

That said, it should have processed it like any other file and listed '/opt/var/log/expanded-syslog.log' instead of 'file("/opt/var/log/expanded-syslog.log" template(t_expandlog));' It's not unreasonable to expect someone may use a template or other modifier to the file statement.

I've no heartburn with excluding it though ... it gets big really quick and as you noted it really is for debugging.

I'll look to improve my rookie sedding to deal with these lines properly

 

[elorimer]

1. Uninstalled and reinstalled 4.1, same problems. The two squibs at the bottom are partial snips from the block source lines in the /'jffs/scripts/uiScribe.d/.logs file.
2. .logs contains a line for crash.log and wlcevent.log, neither of which I have on my 87U (I think this is peculiar to the 86U, yes?)
2. Out of curiousity, since this all requires a USB drive, why are the ui files in /jffs/scripts rather than in /opt directories?

 

[cmkelley]

1. Uninstalled and reinstalled 4.1, same problems. The two squibs at the bottom are partial snips from the block source lines in the /'jffs/scripts/uiScribe.d/.logs file.
2. .logs contains a line for crash.log and wlcevent.log, neither of which I have on my 87U (I think this is peculiar to the 86U, yes?)
2. Out of curiousity, since this all requires a USB drive, why are the ui files in /jffs/scripts rather than in /opt directories?

You have lines for crash.log and wlcevent.log because filters for those logs are in /opt/etc/syslog-ng.d/ -- uiScribe looks for the logfiles listed in the filters, not the logfiles that are actually in /opt/var/log.

I don't think the dcd crashes and wlcevent are peculiar to the 86U. But I guess I don't know that for sure.

 

[elorimer]

ou have lines for crash.log and wlcevent.log because filters for those logs are in /opt/etc/syslog-ng.d/

True. What precisely does it look for: configuration files, destination definitions, filter definitions, or log statements? I have other filters, other log statements, and other destinations, and other configuration files including those in that directory.

 

[cmkelley]

True. What precisely does it look for: configuration files, destination definitions, filter definitions, or log statements? I have other filters, other log statements, and other destinations, and other configuration files including those in that directory.

Gotta ask @Jack Yaz that or delve into the code yourself. I've not looked at it in depth, just had a short discussion with him about it.

 

[Jack Yaz]

Gotta ask @Jack Yaz that or delve into the code yourself. I've not looked at it in depth, just had a short discussion with him about it.

I'm using that command you sent me to produce a list of file targets

 

[cmkelley]

I'm using that command you sent me to produce a list of file targets

Oh yeah, I already forgot about that. Duhhhhhhhhh

@elorimer - it generates the list of log files from the configuration that would be loaded if you restarted syslog-ng, Usually this should be the same as what's loaded into the running copy of syslog-ng, but if you've recently copied files into the syslog-ng.d directory then it will look for those log files even though the filter might not actually be active yet.

Note, however, that it ignores any file statements that don't have '/var/log' in file statement. This is because there is an assumption that you any files you are sourcing (like the logrotate status file) won't already be in /opt/var/log. However, any logs you are sending elsewhere for some reason also won't be shown on the webui.

 

[Jack Yaz]

Oh yeah, I already forgot about that. Duhhhhhhhhh

@elorimer - it generates the list of log files from the configuration that would be loaded if you restarted syslog-ng, Usually this should be the same as what's loaded into the running copy of syslog-ng, but if you've recently copied files into the syslog-ng.d directory then it will look for those log files even though the filter might not actually be active yet.

Note, however, that it ignores any file statements that don't have '/var/log' in file statement. This is because there is an assumption that you any files you are sourcing (like the logrotate status file) won't already be in /opt/var/log. However, any logs you are sending elsewhere for some reason also won't be shown on the webui.

Actually any path/extension should now be shown, but due to my (lazy) pattern matching, if there's anything after ") for the file path (e.g. Template) it is incorrectly included. I should have a patch out tonight

 

[elorimer]

Ok, so it will look for anything that is a (1) destination declaration that (2) is of the form "file("/opt/var/log/*.log"). It won't look for a source in that form, and it won't look for a filter.

 

[Jack Yaz]

0.4.2 is available
Changelog:

More reliable symlink updating
More robust processing of log destinations

Update using u, then launch uiScribe afterwards

 

[L&LD]

0.4.2 is available
Changelog:

More reliable symlink updating
More robust processing of log destinations

Update using u, then launch uiScribe afterwards

Easy update, as usual.

Found a bug for you. If I click on the 'Show All' or 'Hide All' buttons, an 'x' will appear and delete the button name(s).

 

[no_name]

Same here [emoji4]

Sent from my iPad using Tapatalk