• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

How to control stats in access_log

mikemcc

New Pleskian
How can I control what stats are posted to the access_log ? There are so many useless ones there that it's impossible to see whether there are any useful ones. Thanks.
 
What about corresponding statistics software like Awstats or Webalizer?
 
Thanks IgorG.

I'm not a professional coder (just a businessman) but I developed a menuing system so customers can browse and screen video. I used php and MySQL. Mainly a prompt screen calls a processing script, passing a couple of parameters.

My access.log seems to contain mainly GET or POST for the parameters or for the graphics used to brighten up the menus.
In many log entries there are codes like "200 6002" and I can't find any documentation which lists these codes so the entries don't seem very interesting. Do you know of any documentation which helps interpret the log file ?

I can't work out whether and where I can stifle useless messages at source eg in PHP code or Apache parameters.

I suspect that if I can suppress useless log entries, I won't need a stats package to analyze the remaining ones.

Thanks again.
Mike
 
Back
Top