[00:00] In this lesson, we'll learn how to configure alarms for agent events. There are three kinds of events that exist on the agent events table within the controller's database. So we could actually view those here in the designer by opening up the DB query browser and running a select statement to view the table. Looking at the event category, we can see agent, and this is where the activity of a major connection event is monitored like that of a disconnected agent. Then there's task, which is the history of tasks that are run on agents such as running a gateway restart or collecting a backup and you can view task history from the controller's gateway under the agent tasks page in the history tab. The final event type is a metric which is set in the event thresholds page, but we'll talk more about that in a second. Looking at the top of this page, we can enable or disable alarms based on three event categories. These are set to trigger an alarm when a task fails, when an agent stops responding, and when a metrics threshold is met. Those thresholds are configured down below based on a percentage.

[01:03] For example, when an agent's CPU usage is at or above 70%, then the system triggers an alarm and you can configure the threshold for any metric on this list. Simultaneously, a metric event is added to the agent_events table. All of these alarms, whether they are warnings or errors, can have their priorities changed to represent their significance to the user, and to send the alarms to the correct users, you can pass in an alarm pipeline where you wanna send active or acknowledged alarms. I'll go ahead and pass in one to both fields here, and when you're all done configuring this page, then you can click on the save changes button in the top right.