added should fail reference for url monitors (#1345)

* added should fail reference for url monitors

* Remove extra * on URL monitors page

---------

Co-authored-by: Laura Guo <[email protected]>

Author: sujaya-sys

site/content/docs/cli/constructs-reference.md

@@ -324,6 +324,8 @@ The `request` object is a mandatory part of an URL monitor.
 - `url`: The HTTP(S) URL to monitor.
 - `followRedirects`: A boolean indicating automatic following of any `30x` redirects.
 - `skipSSL`: A boolean indicating whether to skip validation of SSL certificates.
+- `shouldFail`: Treat HTTP error codes (4xx and 5xx) as passed. Please note that successful responses still pass. Only failed assertions will cause the check to fail.
+
 - `assertions`: You can define assertions via the `UrlAssertionBuilder`. For URL monitors, only status code assertions are supported. For example:
 
 ### `UrlAssertionBuilder`

site/content/docs/url-monitors/_index.md

@@ -28,6 +28,9 @@ Each URL monitor is defined by its request configuration, which includes the tar
 * **Request method:** Always `GET`.
 * **URL:** The HTTP(S) URL to monitor (e.g. `https://api.example.com`).
 * **IP family:** Defaults to IPv4.
+* **Follow redirects:** Automatically follow 30x redirects.
+* **Skip SSL:** Skip SSL certificate validation.
+* **This request should fail:** Treat HTTP error codes (4xx and 5xx) as passed. Please note that successful responses still pass. Only failed assertions will cause the check to fail.
 
 To validate the response further, you can configure:
 
@@ -87,4 +90,4 @@ new UrlMonitor('hello-url-1', {
 {{< /tab >}}
 {{< /tabs >}}
 
-See the full [Url monitor construct reference](/docs/cli/constructs-reference/#urlmonitor) for more context.
+See the full [Url monitor construct reference](/docs/cli/constructs-reference/#urlmonitor) for more context.