A small but hopefully useful improvement to the EmonHub log view interface in emoncms.
When you open the log view window it starts by loading just over 100 lines. As you keep the view open rather than refreshing and reloading a moving window of 100 lines the log now appends only new log content in an ever expanding way so that it’s much easier to monitor and scroll back through the recent history.
If you scroll up to view content higher up it automatically stops auto scrolling to the latest line. When you scroll back down again it re-engages auto scroll.
Not yet, yes will copy this approach across. I did fix the change of log level in the emonhub log - though I think it might be more useful if that was just a filter of the present view rather than changing the actual log level in emonhub.conf.
The other consideration is how much of the emonhub.log should be loaded when you open the page. I have it set to 10kb at the moment but that could easily be extended to load say 500kb or perhaps even more?
The logfile was previously owned by emonhub, but I saw in the emonhub.service that the service is now run by user pi. So after chown pi: /var/log/emonhub/emonhub.log emonhub could start and everything was fine.
Is it on purpose that pi is the new user to start this service?
After Full update emonhub started fine and worked as expected.
BTW, it’s a pitty that the Upgrade logging shown at the bottom is immediately closing after all update steps. Couldn’t it not better be left visible ‘for a while’/until refresh?
