Kaseya VSA: Policy Objects Series: Alerts

We will be discussing the Alerts Object. In our VSA Basics series, we introduced you to the concept of Policies, and how objects can be configured to automate endpoint settings within the VSA. If you need a refresher on this, you can find it on our channel!

Step by Step:

1. In this video we’ll be discussing the alerts object so let’s get into it.
2. The alerts object allows you to be informed on items that Kaseya refers to as alerts these include agent status whether the machine is online, offline, or if remote control is disabled by the end-user.
3. Application changes if an application is installed or removed.
4. Get files if a change occurs to a machine’s get files folder.
5. Hardware changes.
6. Low disk alerts when a machine reaches a specified percentage of free space.
7. Event logs monitoring for specific event log type and criteria such as the source event ID description.
8. Agent Procedure failures.
9. And lastly protection violations which you can learn more about in the agents module under protection.
10. As with monitors alerts allow you to configure the creation of alarms, tickets, emails, and script execution.
11. So, let’s go ahead and take a look at setting up an alert for agent status, low disk, and event log.
12. So let’s select add alert, let’s select agent status, let’s check agent has not checked in for, and let’s do five minutes. (you have a couple other options here)
13. And for rearm alert after let’s do one hour let’s also select alert when agent goes online. This alert now triggers after machine has been offline for five minutes and if the machine is offline after an hour it will trigger again it also gives you an alert when the machine comes back online.
14. Let’s select add, let’s do low disk, select add alert, low disk and let’s set the percentage to 10 percent. This alert now triggers once a machine is at or below the 10 free space threshold.
15. Let’s do add alert and let’s select event log.
16. Let’s select the log type that you want to look to see this event ID occur.
17. I’m going to select application and let’s select the event set that we are looking for.
18. Select the drop-down and I’ll grab my weber app crash event ID that I’ve created. I’m going to go ahead and select error, critical, and warning, do know that depending on the type of event that you’re looking for not all three of these will be necessary and it could even be others and by default alert when this event occurs once it’s selected.
19. What this alert will do is anytime the event IDs that are matched within this event set occur on a machine it will trigger.
20. Let’s go ahead and select add and that does it for this video.