LMS-Community/slimserver

Analytics plugin: reporting delay is dependent on debug setting

terual opened this issue · 1 comments

A lot of users use the debug setting for plugin.analytics so they can see what is being reported. According to

Slim::Utils::Timers::setTimer($id, time() + ($log->is_debug ? 3 : REPORT_DELAY), \&_report);
the delay timing is reduced when debug logging is used.

To solve this maybe we can also show what data is being reported to info logging, that way users can see what is being reported and still use the 4 minutes delay. And when you are a developer and want to quickly check what is being reported you can use the debug logging for the plugin.

Right! Too many people are watching logs. I thought I was the only one doing this 😁.