Facebook
Twitter-
Please be aware: Kaspersky Anti-Virus has been deprecatedWith the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
-
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
How to control stats in access_log
- Thread starter mikemcc
- Start date
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
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