One of the biggest reasons for having Automate is it allows you to monitor systems and processes. You can have it alert you about various events and activities. There are some built-in monitors that come with it that are built-in collections called service plans.

We cover all things monitoring in this section, including:

- The two core types of monitors in Automate (internal monitors and remote monitors) and what the difference between them is
- Alert templates (the set of instructions on "what do I do if it triggers?")
- A couple of case studies where we'll build some specific monitors and figure out how to make everything work together, including one concerning software installs (a way to detect that a piece of software that should be there is not there)
- Best practices: what you should turn on, what you shouldn't, what to expect
- The built-in service plans (for better or worse.) They're a little weird and will need some tweaking at first.
- Auto fix actions (what you would do in the event that you want something to remedy itself as a result of a monitor triggering. A great example of that would be disc space. Disc is full, run a disc cleanup.)

If you want to learn more about monitoring and get the ins and outs, then this is the course for you. I definitely recommend that you jump in.

You'll also find this link over in the community as well as people discussing it because monitoring is a pretty important topic.

Feel free to jump right in. I'll be around in the community as well, so leave comments, suggestions, or questions over there and we can discuss it more in-depth.

Happy automating!

Complete and Continue