Forwarded to devs httpsd_access_log swamped by grafana log entries

[TomBoB]

TITLE:

httpsd_access_log swamped by grafana log entries​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

CentOS Linux 7.7.1908 (Core)‬
Product Plesk Obsidian
Version 18.0.21 Update #5​

PROBLEM DESCRIPTION:

The httpsd_access_log file is being flooded by entries of the grafana monitoring. Which makes looking for real entries near impossible.​

STEPS TO REPRODUCE:

open httpsd_access_log log file and try to find proper log entries.​

ACTUAL RESULT:

127.0.0.1 - - [04/Jan/2020:12:39:36 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 130 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:39:38 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 120 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:39:41 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 127 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:39:47 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 137 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:39:52 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 126 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:39:52 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 110 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:03 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 127 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:03 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 132 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:04 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 130 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:05 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 133 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:14 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 126 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:14 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 120 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:17 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 137 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:18 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 110 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:33 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 132 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:35 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 133 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:36 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 127 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:36 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 126 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'
127.0.0.1 - - [04/Jan/2020:12:40:39 +0100] "POST /modules/monitoring/public/index.php/AuthCode/query HTTP/1.1" 200 130 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/AuthCode/query' '' '/usr/local/psa/admin/htdocs'

thousands of grafana log entries exist, effectively hiding the few proper entries​

EXPECTED RESULT:

show only proper log entries​

ANY ADDITIONAL INFORMATION:

​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

Why the availability of entries from the module is a problem?

To search for necessary entries, you can use grep or exclude entries from the module if necessary, for example like this:

# tailf /var/log/plesk/httpsd_access_log | grep -v '/modules/monitoring\|/modules/grafana'

 

[TomBoB]

Hi Igor,

it's not a problem per se, am aware how to search the logs. I just find them unnecessary (even a nuisance) as I don't see what is gained by having them. To me logs are meant to provide useful information. And I fail to see the usefulness of those thousands of entries.

But no matter, you are correct, they aren't actually causing any damage.