Issue Plesk Monitoring generates thousands of localhost requests in httpsd_access_log

[Azurel]

Server operating system version

AlmaLinux 9.8

Plesk version and microupdate number

18.0.80#2

I noticed that /var/log/plesk/httpsd_access_log is filled with thousands of requests generated by the Plesk Monitoring extension, for example:

127.0.0.1 - - [19/Aug/2026:10:54:20 +0200] "POST /modules/monitoring/public/index.php/Sa_....oY/query HTTP/1.1" 200 129 "-" "Go-http-client/1.1" "-"'/modules/monitoring/public/index.php/Sa_....oY/query' '' '/usr/local/psa/admin/htdocs'

The requests are coming from 127.0.0.1, return HTTP 200, and occur at a very high frequency (in this example every ~2 seconds). The log has grown to around 75 MB in than two weeks. Previous archived files of httpsd_access_log are around 300KB.

# ls -lah /var/log/plesk/httpsd_access_log*
-rw-r--r-- 1 root root  75M Aug 19 12:10 /var/log/plesk/httpsd_access_log
-rw-r--r-- 1 root root 289K Jul 31 03:25 /var/log/plesk/httpsd_access_log-20260731.gz
-rw-r--r-- 1 root root 240K Aug  3 03:44 /var/log/plesk/httpsd_access_log-20260803.gz
-rw-r--r-- 1 root root 328K Aug  6 03:05 /var/log/plesk/httpsd_access_log-20260806.gz

I have this questions:

1. Why are these internal Monitoring requests written to the regular httpsd_access_log at all?
2. Is the very high polling frequency (multiple requests every few seconds) expected behavior, and is there a way to reduce it?
3. Why is my httpsd_access_log not logrotating?

 

[Sebahat.hadzhi]

Why are these internal Monitoring requests written to the regular httpsd_access_log at all?

As far as I am aware, this is expected behavior. Monitoring calls go through the same web server, thus, they get recorded in the same log file.

Is the very high polling frequency (multiple requests every few seconds) expected behavior, and is there a way to reduce it?

When you observe that behavior do you/another admin interact with Monitoring in Plesk panel?

Why is my httpsd_access_log not logrotating?

Can you please confirm what's the current logrotate confirmation and do you observe the issue with that particular file only or with other logs as well?