[LOGTOOLS-24] Improvements to make the Log Viewer more useful for system administrators Created: 05/Apr/17  Updated: 10/Apr/17

Status: Open
Project: Magnolia Log Tools
Component/s: None
Affects Version/s: 1.x
Fix Version/s: None

Type: Epic Priority: Neutral
Reporter: Lars Fischer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: log, log4j
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
Template:
Epic Name: Log tools for admins
Acceptance criteria:
Empty
Date of First Response:

 Description   

These are some good proposals to increase the usefulness of the log viewer app for real day to day use. See the linked support ticket for more information.

Don't ignore files not having "log" in the name

Current implementation shows only files of magnolia.logs.dir with "log" in the name. This means that catalina.out is not shown (and that's often the most important log file).

Setting the log level for more than one class at once

It should be possible to select more than one class in the list and set a new log level. Another option would be to set the log level for a package name (see below).

Set the log level for a package

Sometimes it would be very handy to change the log level for a package instead of single classes.

Paging the view with the keyboard

Right now its only possible to scroll in chrome with the scroll bar - but not with the page-up/-down, cursor-keys...

Select parts of log views and copy them

It must be possible to mark entries and copy/paste them.

Update the current log view (like tail -f)

It's very important for test-persons to be able to have a look at the current log (eg catalina.out) while testing specific functionalities. Therefore the display of th ecurrent log should be an actual view which will automatically be updated. It should be possible to suspend automatic updating and start it again. In addition, the view should be scrollable.



 Comments   
Comment by Jan Haderka [ 10/Apr/17 ]

Set the log level for a package

Setting the log level for more than one class at once

... should be covered by LOGTOOLS-25

Paging the view with the keyboard

... should be covered by LOGTOOLS-27

Update the current log view (like tail -f)

... should be covered by LOGTOOLS-26

Select parts of log views and copy them

This is already possible in current version (logtools v. 1.0.3)

Don't ignore files not having "log" in the name

We don't specifically ignore anything. In fact we don't even know. What we look at are the loggers into which Magnolia writes directly and we provide output to those loggers.
While I agree that it would be useful at the time to look at catalina.out or other kind of server log when running on different kind of servers than Tomcat, it would require us to go outside of our sandbox and tap into the file system of the server and try to discover where server logs are stored, most likely by reading server configuration. In short we would have to go outside of the boundary of the webapp and as such risk potential security break in the future should someone find a way to abuse this going outside to show some other files.
On top of the above explained security concern, feature would be fragile due to multiple different ways of configuring location of the logs in different servers and different version of servers. Last but not least we would be also duplicating functionality of the servers themselves. All currently supported servers allow browsing of the log files online when management console of said servers is installed, enabled and configured. To see server log files, sever management console and not Magnolia log viewer should be used.

Generated at Mon Feb 12 06:01:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.