Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log Viewer, used to monitor cron tasks, performance #2473

Closed
mattab opened this issue Jun 6, 2011 · 2 comments
Closed

Log Viewer, used to monitor cron tasks, performance #2473

mattab opened this issue Jun 6, 2011 · 2 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jun 6, 2011

Now that we have simple Logging mechanism let's showcase how awesome it is.

Steps:

  • Add Log:: calls at end of archive.php, one line:
    done: 21/21 100%, 2 v, 21 wtoday, 21 wperiods, 84 req, 78138 ms, 1 errors
  • Create new plugin (for the marketplace or core?), disabled by default, that when enabled will add a new tab in the admin UI under Diagnostic to visualize the Logs
  • would let one browse the raw logs, read from the DB or File.
    • Automatically displays per-tag filters, if there are records for given tag (to find tags, we can do "select distinct tag from log"
    • The first link would be the one for "View auto archiving logs" which filters the log to show only the archive.php log detail
  • would we use a Datatable to view the logs and have paging, search, etc.?

By the way, while doing the Log viewer we may want to change it to log datetime in the system timezone, as requested by few users: #3029

@anonymous-matomo-user
Copy link

we might also pass collected error messages to such an api call, so they can be stored in the database and displayed right in the web interface...

i would tend towards two separate calls, one for starting and one at the end, then the runtime can be derived from that right on the php side, and we would also tell if the job is still running or maybe died unexpectedly... and it would keep most of the handling code on the php side and not add much complexity to the script.

@mattab mattab added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab
Copy link
Member Author

mattab commented Feb 18, 2015

see #7239

@mattab mattab closed this as completed Feb 18, 2015
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Feb 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

2 participants