Is there any other way to monitor url's other than using the url_response probe ?

• Release: 8.51 or higher
• Component: UIM - URL_RESPONSE

e2e_appmon

There is the e2e_appmon transaction scripting probe which can look for text on a page, click buttons, etc... and report response time, failures, qos, etc...
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/e2e-appmon-e2e-application-response-monitoring.html

net_connect

There is also the net_connect probe which can test whether a service is listening on port 80/443:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/networking-infrastructure/net-connect-network-connectivity-monitoring/net-connect-network-connectivity-monitoring-release-notes.html

logmon

Another option is the logmon probe in combination with a shell script or batch file run using command mode.

That script/batch file could call the OS curl command to fetch a URL and report on the response or HTTP status, etc...
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/logmon-log-monitoring.htmlhttps://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/logmon-log-monitoring.html

and

https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?MessageKey=8538d2ff-6e51-459c-a5a0-53a91686894c&CommunityKey=170eb4e5-a593-4af2-ad1d-f7655e31513b&tab=digestviewer#bm8538d2ff-6e51-459c-a5a0-53a91686894c

url_response endpoint response monitoring
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/url-response-url-endpoint-response-monitoring.html

Treating a 401 error as valid is not supported by the url_response probe.

Even if the given URL which requires authentication is 'accessible,' it does not guarantee that the target page is available. Therefore, it will be incorrect to report a URL as 'available' if a 401 error is received.

The best option is to ask the customer to provide a username and perhaps a complex password that they are comfortable with so that they can be configured in the probe for Windows NT authentication (since that is what is being used by the website).

url_response troubleshooting
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/monitoring/systems-and-service-response/url-response-url-endpoint-response-monitoring/url-response-troubleshooting.html