Advanced HTTP Synthetic Monitor
This guide provides instructions on how to create an HTTP(s) Synthetic Monitor leveraging many of the more advanced features. These parameters will help you to fine tune your monitors in order to get the most out of them.
Using the instructions provided in this document, you can create an HTTP(s) Synthetic Monitor to validate and alert on the health and performance of your HTTP(s) applications.
Configure an HTTP Monitor
Step 1: Create a new HTTP Monitor.
Log into the F5® Distributed Cloud Console.
Navigate to either the
Observabilityworkspace tile or menu.
Note: The homepage is role based, and your homepage may look different due to your role customization. Select
All Servicesdrop-down menu to discover all options.
Add HTTP Monitor.
Step 2: Configure Metadata.
Step 3: Configure what to monitor.
Step 3.1: Set the monitor URL and interval.
URLthat you would like to monitor.
Set the monitor frequency
Intervalfor how often you would like the monitor to run from each source region configured later in the form.
Step 3.2: Optionally set
Request Headers` .
Note: Some applications require specific headers to be present either for functionality or logging purposes.
Keyas for the header name.
Valueas the header value.
Add itemif you require additional
Request Headersto be added.
Step 3.3: Optionally update the
Valid Response Codes.
Note: A monitor will be considered healthy by default if the response code is within the 200 or 300 response code range.
Valid Response Codesallows for the use of wildcards(*) so that the user does not need to manually input every allowed response. For example,
2**covers any 200 response code. If
202was explicitly set with no other codes then all response codes other than
202would be considered
- Add, remove, or modify the
Valid Response Codesto match what you expect from your HTTP(s) endpoint.
Step 3.4: Optionally set an
SNI Host Override value
- Modify the
SNI Host Overridein order to send an SNI value other than the URL host value.
Step 3.5: Optionally set a
Response String Match
- Modify the
Response String Matchfield to a value that is required to be within the response body of the monitored endpoint. If the response does not include the
stringthen it will be marked
Critical. The example below would match
Step 4: Configure where to monitor from.
Note: Each source
regionadded will monitor the endpoint configured for the monitor. The combined health from all regions will generate the overall monitors
- In the
Add Itemto begin adding sources for the monitor.
Select the desired
Providerfor which you would like to source the monitor from.
Providerselected, click the
Regionsdropdown and select which
Regionyou would like the monitor to run from.
Add Itemif you would like to add additional
Regionsfor the current
Applyto add the current
Regionsto the monitor.
Back in the primary
Add Itemand follow the steps above if you would like to add additional
Step 5: Configure how to monitor.
Response Timeout in Secondsto control how long a monitor will wait for a response before considering the
Number of consecutive test failuresto control how many
Criticalresponses must be received before the
Globalhealth changes to
Number of Failed Locationsto control how many source
Provider-Regionsmust fail before the
Globalhealth changes to
Ignore Cert Errorsto have the monitor exclude TLS errors when determining the health.
Follow Redirectsto have the monitor follow redirects before determining health.
Save and Exitto save the new HTTP Synthetic Monitor.
Step 6: Setup Alerting.
Synthetic Monitoringcan be configured similar to other F5® Distributed Cloud services following the Alerting how-to guide.
Optionally filter your
Alert Policyto only send notifications to the receiver based on alerts coming from
Synthetic Monitoringby either matching the
Synthetic-Monitorsor matching the