Before you can configure the system to send alerts concerning server latency, you
need to have created an Analytics profile to collect application statistics locally
(Statistics Logging Type must have
Internal selected). To set up email alerts, the default
analytics profile must specify an SMTP
You can configure the BIG-IP system to send an alert when
server latency is high.
On the Main tab, click
Tip: If Analytics is not listed, you need to
provision Application Visibility and Reporting (AVR) first.
The Profiles: Analytics screen
Click the name of a previously created Analytics profile, or create a new one.
Select the Custom check box.
For the Statistics Logging Type setting, verify that
Internal is selected. If it is not, select it.
Selecting Internal causes the system to store statistics locally,
and you can view the charts on the system by starting at the Main tab, and clicking .
To send email alerts, specify an SMTP Configuration
(this can only be done on the default analytics profile).
If you created a new profile, configure SMTP later.
For the Notification Type setting, select how you want the system
to send alerts and notifications.
When you select a notification type, the screen displays the Alerts and Notifications
Configuration area, where you can indicate the criteria for alerts and
||Select Syslog if you want the system to send
notification and alert messages to the local log system. You can view the messages
on the screen.
||Select SNMP if you want the system to send notification
and alert messages as SNMP traps. You can create the trap by clicking
Configuration can be found here ( ). Enabling SNMP automatically sets up Syslog notifications,
||Select E-mail if you want the system to send
notification and alert messages to email addresses. Type each email address in the
Notification E-Mails field, and click
Add to create the list. This option requires that the
parent analytics profile includes an SMTP configuration.
In the Alerts and Notifications Configuration area, for the Add New
Rule setting, define the rule that determines when the system
sends an alert about server latency.
For Alert when, select Average Server
Select above, and then type the number of
milliseconds (the threshold) that is too high for your application. For
example, type 100 if you want to receive an alert
when latency is above 100 for 300 seconds.
It is a good idea for you to get familiar with the typical average
server latency of your application so you can recognize high server
Select Application as the granularity level to
which the threshold applies.
The rule is added to the list of Active Rules.
If you need to configure SMTP (if sending alerts by email), click the default
analytics profile on the Profiles: Analytics screen.
For SMTP Configuration, select an existing
If no SMTP configurations are listed, click the
here link to create one. When you are done,
you need to select the configuration you created in the default
The system sends an alert when the average server latency of an application exceeds
100 ms for 300 seconds. Another alert is sent when server latency changes back to under
100 ms for 300 seconds.