Question Watchdog v3 - New service configuration

[Alban Staehli]

Server operating system version

AlmaLinux 8.10 (Cerulean Leopard)

Plesk version and microupdate number

18.0.68

Hi,

I've followed the following instructions for Watchdog to add new services configuration: Instruction - How to add a new service to the watchdog extension
Nevertheless, since Watchdog v3 upgrade, these new custom services are not being monitored (while still being listed).
I attempted to look at the mysql table within the Plesk database, but the table module_watchdog_service no longer exists.
Would you know where to look at? in which mysql table?
Thanks.

 

[AYamshanov]

The instruction applies to Watchdog 2.x / Monit 2.x. Watchdog 3.x uses Monit 5.x, but new Monit has slightly different conf.file syntax. Previously, Watchdog was a Plesk module and had more internal dependencies with Plesk; it was converted to an extension and now has a slightly different data structure.

For PHP-FPM services, we have a UserVoice request (Manage all the additional Plesk PHP-FPM versions in Watchdog Monitoring extension on modern OSes, systemd makes this work better; it detects a service down event and restarts a service much faster.

Could you please provide more details on what additional services you want to monitor, why it is essential, and why systemd can't do this work? After the release, we are collecting feedback now; feel free to share all your thoughts.

 

[Alban Staehli]

I just voted for the PHP-FPM in watchdog. What I'm after is monitoring the clamav milter, which obviously you do not formally support.