BGP in HTTP(S) and Page Load Tests
In previous releases we provided the option to include network layer data in web tests by enabling ping and trace route in HTTP(S) and Page Load tests. This allowed us to quickly correlate application and network metrics to identify the root cause of an application's performance or availability issues.
Expanding on our cross layer visibility we can now include BGP data in web tests as well. Allowing us to further improve the time it takes to identify the root cause of issues as originating in either the application, network or routing domain.
Where previously you would need to create a separate BGP Monitor test you can now examine the same BGP data in an adjacent tab on the results page itself. No need to jump between test views!
When included, BGP data will be visible as an additional tab in the test results page.
Putting it altogether, we can now analyze all layers of information relevant to a target application's health on the same screen, including
Application metrics and Network Ping metrics in the Results tab.
Network Trace metrics in the Path View tab.
To add BGP data to an HTTP(S) or Page Load test turn the switch to "Enable bgp monitoring" (disabled by default) and enter the necessary details as you would for a regular BGP Monitor test including health options for Allowed ASN(s), RPKI status and Reachability (Advanced Options).
Refer to the KB for more details on configuring BGP Monitor tests.