Ventas de GLP de Productores e Importadores
CAPÍTULO 5: DESARROLLO DEL MODELO
values by 200%. This has to be measured for the whole server (IP address), not for any particular URL.
We will have to configure the baseline comparison threshold to 3 (300%) and specify that we want to monitor server IP addresses and software services. Additionally, we may want to receive information about the number of clients who use a specific software service on a given server. For that purpose, we will select the number of unique clients as an auxiliary metric. Finally, we need to ensure that detected behavior is a real problem. We do this by making sure that server time does not go to normal before 30 minutes. Then we raise an alert after that period of time. We assume that you want to receive notifications about alert states by e-mail.
1. In the RUM Console, select Alerts from the top menu. The Alert Management window appears.
2. On the Alerts tab, click User-defined.
3. Click Add Alert to access the alert configuration wizard. Specify Basic Settings
4. From the Alert type list, select Generic performance.
5. In the Alert name box, specify a descriptive name that will later help you identify the alert. 6. Optional: Provide a short description of the alert.
7. Optional: Modify the default assignment of the alert to the report servers.
By default, the definition is assigned to all available report servers. 8. Click Next.
The Define Triggering and Propagation Conditions screen of the alert definition wizard is displayed.
Define Triggering and Propagation Conditions
9. On the Define Triggering and Propagation Conditions page of the wizard, on the Detection settings tab, set the values that will trigger the alert.
a. Click Add dimension to add a dimension selection box to the Monitored dimensions section.
b. Move the mouse cursor over the dimension name and click it to display a complete dimension list.
c. From the dimension list, select Server IP address.
d. Repeat Step 9.a [p. 60] through Step 9.c [p. 60], but choose Software service instead of Server IP address.
e. Leave the default dimension filter settings.
The default settings ensure that the alert will not operate on synthetic traffic. Do not add any other dimension filters, unless, for example, you want to limit the applicability of your alert to specific server IP address range or a specific software service. f. Leave the Comparison mode set to Single (default setting).
g. From the list of metrics, select Server time.
h. Click Add condition and choose a Value condition from the list.
i. Set the threshold value to 0.15 s to specify that anything below 150 milliseconds will not be considered a problem.
Leave the default relational operator (greater than) selected. j. Click Add condition and choose a Baseline condition.
Note that both value and baseline condition have to be fulfilled for the alert to be raised. k. Select the baseline type.
The default type is average baseline. For more information, see Baseline Modes in the
Data Center Real User Monitoring Administration Guide.
l. Set the baseline multiplier to 3 to specify that the detected value needs to be 3 times the baseline value.
Leave the default relational operator (greater than) selected. m. Define the auxiliary metric.
Under Auxiliary metric, select Unique users from the metric list. 10. In this example, you do not need to configure the Output filters for the alert. 11. Click the Propagation settings tab to specify how the alert will be propagated.
a. Set Raise after to 6 to indicate that the alert is to be raised after 6 intervals (the thresholds need to be exceeded in 6 consecutive monitoring intervals, which would be 30 minutes if the monitoring intervals are the default length of 5 minutes).
b. Select Delayed processing to indicate that we do not want to activate the alert until baseline values are calculated.
12. Click Next.
The Configure Alert Notifications screen of the alert definition wizard is displayed. Configure Alert Notifications
13. On the Configure Alert Notifications page of the wizard, specify the notification message template.
In the template, you can use generic textual information and elements selected from the list hidden under the icon. When a notification is sent, these elements are substituted with the real-traffic data served by AMD.
For example:
High server time of the service running on server {6} ({7}), via software service {5}.
Server time values - current: {17} {18}, threshold: {19} {18}. The number of users connecting to the service: {20}.
When delivered, the message may look like this:
High server time for the service running on server 10.10.10.1 (MyServer), via software service MyService.
Server time values - current: 330 ms, threshold 150 ms. The number of users connecting to the service: 11.
14. Assign and enable the notification for a selected user.
If you want to receive a notification by e-mail, go to Actions ➤ Enable notifications for a specific report server user listed on the Users tab. If you skip this step, the alerts will be written only to the alert log.
15. Click Next.
The Review Summary screen of the alert definition wizard is displayed. Review Summary
16. On the Review Summary page of the wizard, verify your alert settings before you apply them to the report servers.
If you need to change anything, click Previous to go back to the appropriate page of the wizard.
17. Click Apply.
On the pop-up window you can select the option to save your changes as a draft, if you intend to make more changes now, or to immediately publish the changes if you want to make your changes live now.