Linux monit with the transition to systemd?

Good day colleagues. Then came the task of translation servers with ubuntu 14.04 to 18.04.
On 14.04 for monitoring of services were used monit, but if I correctly understand 18.04 it can be replaced by systemd. On account of the control processes is no problem, but in cases when you need to restart the service or the network card falls on the local network , then systemd was able to find only a very spike options. And how they think via systemd can be implemented provrka of the network card and dostupnosti Internet resources ? There are physical and virtual interfaces.
I would very much like to hear your opinion on this issue. Alternative options are welcome. Thank you.
Now monit tied these checks
check network eth0 with interface eth0
 onreboot nostart
 start program = "/sbin/ifup eth0"
 stop program = "/sbin/ifdown eth0"
 if failed link then restart

dhclient_eth0 check process with pidfile "/run/"
 depends on eth0
 onreboot nostart
 start program = "/sbin/dhclient -1 -v -pf /run/ -lf /var/lib/dhcp/dhclient.eth0.leases eth0"
 stop program = "/sbin/dhclient -r -v -pf /run/"
March 12th 20 at 08:41
2 answers
March 12th 20 at 08:43
I suspect you somehow misunderstood.
monit monitoring system.
systemd is the init system.
All he had understood correctly. - chadd.Roberts commented on March 12th 20 at 08:46
systemd copes with the condition monitoring service, and restart. But after my research it became clear that control of the equipment he's troubled. - Trent54 commented on March 12th 20 at 08:49
March 12th 20 at 08:45
In Ubuntu, c 17.10 the network looks netplan. And monit is monitoring and restart, it does with systemd-networkd is not connected.

Distortion network is just a weird crutch in itself.
from netplana abandoned, as there is very gemorno configuration for VPN if you managed to win, I'd be happy to hear the options as is) - Trent54 commented on March 12th 20 at 08:48

Find more questions by tags systemdUbuntuMonitoringDebianLinux