You can get around this problem by using panels. The panels are a little buggy, but you can create custom views mixing charts, maps, logs... anything! You can lock the Panel so that you cannot inadvertently change anything (which is easy to do).
Double click Panels, then add a new panel... we'll call it "LogViewer". Then, right-click on LogViewer and select Settings.
[There's a bug where sometimes if you create a new panel, it will not have the title bars, so you cannot actually associate any logs, maps, etc. with the panel; no choice it seems but to delete the panel and try again. I usually just copy an existing panel to avoid this bug, cuz it's really irritating.]
The trick to making panels work is double click panels, right-click on your panel in question, select settings. UNLOCK, click apply. Make changes, click apply. LOCK, click apply. If you do not follow this procedure, you'll probably never get them working right!. Click apply ALOT!! LOCK the panels when you're done messing with them, or they'll get messed up (due to some bugs, I think).
When the Title Bars are turned on, you can "slice" the window horizontally & vertically into small, well... panels! In each "slice", you can insert a map, chart, log, etc.. even another panel (yikes... you can even add the panel you're working on, which is like looking from one mirror into another).
Now put your Log file (event log, syslog, whatever...) into one of those window slices. Select the fields you want (I get rid of the Flags field). Select the sort-order that you want. Now click Apply, then *lock* the panel!
At that point, you'll go to the LogViewer panel to look over your syslogs rather than going to the log itself.
To take this a step further, I create a bunch of syslog rules that separate syslog messages into various groupings... ie. by device, device types, devices that are in a geographic area, log message types (such as ospf, wireless, bgp, etc..). To do this you have to create a log file under logs, then create a notification with the type: log, and the Target log set to the logfile you created.
Then, you create syslog rules to sort things as appropriate... I'll do a log of passthrus so the same log message may go into several different log files. If I get an OSPF message from one of my Ciscos, it goes into a "Cisco Routers" logfile, then passes through and goes into an "OSPF" logfile, then passes through and goes into a logfile for all the devices at that location, then passes through and goes into a "catch-all" logfile, the master syslog.
Then you can create panel views that focus on different data-sets for a piece of equipment or a grouping of equipment. One page can display the logs for those devices, a network map showing how they're connected together, and some performance charts like bandwidth utilization and ping response times.
You do not have the required permissions to view the files attached to this post.