Event trigger is defined when a specific activity raises the alarm signal. Let’s use the below scenario to elaborate the set-up.
To monitor the CPU utilization of a DGS-3120-24TC device using the following alert rule:
- Info Event: 50% ≦ CPU utilization < 60%
- Warning Event: 60% ≦ CPU utilization < 70%
- Critical Event: 70% ≦ CPU utilization
Step 1: Select sensor type to create a new sensor
- Go to System > Sensor Settings
- Choose CPU Utilization from the pre-defined sensor at the left
- Then click on New Sensor on the right
- At this point, a sensor creation wizard will pop up
Step 2: Set sensor information
- Provide sensor name and other info for this new sensor then click on Next
Step 3: Set alert rule
We will explain one event in details.
For Info Event:
- �Enable the alert event by selecting ON
- Set the trigger point with ≧ 50%
- Set the trigger repeat time to 1 time
- Select ON to enable Escalation: event will escalate to the next level (i.e. Warning in this example) if the escalation rule is met
- Set escalation rule at 3 times: when 3 times of Info Event took place, the alert will escalate to Warning Event
Same method as above for the Warning Event and Critical Event.
Step 4: Apply the sensor to the device you wish
- Check the box for DGS-312-24TC to select it
Sensor setting steps are done. Now let's review the settings.
We can review the newly created sensor to see if it is working fine.
- Go to System > Sensor Settings > CPU Utilization
- The new alert event we just created is now listed at No. 3. We can see that “C”- Critical, “W”- Warning, and “I” - Info alert events are set
You can also review the alert event status of this device.
- Go to Monitor > Device View and find DGS-3120-24TC
- �To see more details of the Critical Event of this device, mouse-over the red-box
You can see the event took place at 2014-05-27 18:05 when the CPU utilization is more than 70% for the DGS-3120-24TC.