Question Monitoring a Plesk Server (services, domains, etc.) with Zabbix

[cpulove]

Server operating system version

Debian 12

Plesk version and microupdate number

Plesk Obsidian v18.0.67_build1800250205.19

The last days I was searching for the best way, to monitor a plesk server (built on debian 12) with zabbix.

I am hosting my plesk server on a proxmox ve. My zabbix Server is running on a VM, also on a proxmox ve, but local. Public access to my zabbix Server is granted by an cloudflare tunnel.

As I understood, I have to install an zabbix agent on the debian of my plesk server, right?
And this agent then communicates passive or active with the zabbix main server.

I found a template and script for Plesk here: Plesk monitoring and integration with Zabbix
The Template states 6.0, but my zabbix server is 7.2, so I am not sure, if this will work.

Unfortunately my google search did not bring up any detailed instructions, how to set up all this for the specific uecase with plesk.

If there is another way, to monitor the plesk server with email notification, etc. pp. I am open to discuss the cons and pros.
I knew the possibilities of Montitoring 360, but I really like to try zabbix, as I can monitor other containers and vms from there and also get monitoring for specific services like apache, php-fpm or mysql.

So any help an suggestion would be warmly welcome!

 

[scsa20]

Considering those templates are community made templates, all I can say is: give it a try for the template for version 6.0 and if it doesn't work to open up an issue on their github.

As for other ways of monitoring, Plesk does have some native ways of monitoring but it's pretty much reliant on itself to actually work (so if plesk has any issues you probably won't be notify), you'd be better off using the native tools on proxmox for basic monitoring for say cpu, memory, network, etc.

 

[Faris Raouf]

That template works fine on 7.2 (7.2.5 tested just now), although three of the tests (Default Plesk Page Visible) will most likely fail out of the box. None are important and I'm not even sure why they exist.

The tests are pretty simple though. Essentially they mostly make sure services are running.

What you really need is how many email messages are in the queue, how many bounced, how busy is the apache server (slots etc), and so on and so forth, and this particular template doesn't offer that. It is great that the author created it and I'm grateful to him. I'm just saying that it isn't a 100% complete template for 100% Plesk monitoring as it doesn't look at the aspects that are mostly likely to need investigation if they go out of bounds.

I don't use Zabbix myself. I'm just investigating how hard it will be to move from my current setup to Zabbix, which has a nicer UI. And I happened to test the very same Plesk template today, hence I was able to let you know that it works.