• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

[IDEA] Piwik Log Analytics (done the right way)

Somebody1

New Pleskian
Okay, so I have the idea to implement piwik on my Plesk installation, for all users. Why? Because AWstats and Webalizer are generating plain HTML-logfiles. Great for some quick overview, but I want insights. And Piwik has more capabilities to log accurately.

The idea is to install Piwik in /var/www/piwik, and make an alias for all users to it. (like /plesk-stat/piwik) Now you don't have hundreds of separate Piwik installation, but one. However, I haven't find out the best permissions. Since AWStats and Webalizer just use HTML-files which are copied to the users analytics directory upon creation, it's a different thing. By the way, Piwik is configureable to accept a plain HTTP-login, so it integrates well.

So that's a bit of the basic configuration, but now the analytics. How are we going to insert the tracking codes into all the client websites? Great news: not. We are going to use Piwik's log importer for that. Fantastic news: The same script supports piped log importing for real-time analytics (from all websites), if you want to go that far. Parallels guys, why didn't this great stuff didn't make it into Plesk allready?

So the idea is currently to make a wrapper for the log importer and schedule it daily.

What are your thoughts on this?
 
Hello Igor,

I found the problem, it was my fault. The firewall was configured with restriction to several ports in localhost. Now it is properly configured and it works well.

Thanks.
 
Back
Top