In Connectwise Automate monitors are the system that monitors agents and the database for specific states. It will automatically trigger based on the criteria provided, and can preform any number of tasks based on the assigned action.
There are two types of monitors. Internal and Remote monitors. Internal monitors are internal to CWA itself. They check the database and respond accordingly. Remote monitors are remote to the CWA server. They run on the targeted agent, rather than looking at CWA’s database.
Lets start by talking about remote monitors. Remote monitors are useful for checking the target machine, or checking something from the point of view of the target machine. For example, you may want to attach a monitor to a machine to check to see if a service is running. You may also want to attach a monitor to a machine to ping a network device that cannot have an agent on it. I have used remote monitors to ensure VPNs are working, to check the contents of a website for errors.
An internal monitor will keep an eye on the CWA database for a state you are looking for. This is normally used for less time sensitive activities, or checks that might require mixing multiple pieces. One example that is built in is the offline server monitor. It checks the CWA database for servers that haven’t checked in nor had a heartbeat in over a certain amount of time. Obviously a server can’t report that it is offline, so it must be reported on by an outside source. Of course another computer at that location could do it, but what if the Internet is totally out? This makes internal monitors very powerful. They also don’t take any resources from the client device, so if you used it to, say, detect a stopped service, it would take until the next time CWA inventoried the services before it would notice the change, but it couldn’t possibly hurt the target computer.