Design Pattern for Module that continuously checks if other modules in the system are working?

I am implementing a java project where there are multiple decoupled modules interacting with a shared service (database/web service).

There is a health checker module that continuously polls all the modules to see if they are functioning or not. If a module is found to be inactive or not functioning properly, the health checker module performs a repair and restarts it.

Which behavioral pattern would this belong to?