HTTP Monitor - Monitor Web Endpoints and APIs

the http monitor allows you to keep track of the availability and performance of web endpoints and apis by regularly sending http requests and evaluating the responses based on configurable criteria creating a new http monitor navigate to synthetic monitoring > monitors click on add new from the monitor type dropdown, select http monitor web endpoints and apis basic settings url specify the full url of the endpoint or api you want to monitor monitor name assign a descriptive name to identify the monitor check interval define how frequently the monitor sends requests to the endpoint to check its status and response timeout set the maximum amount of time the monitor will wait to receive a response from the endpoint before considering the check unsuccessful notification settings configure where notifications should be sent if the monitor detects downtime or failures select one or more notification channels in this section to receive alerts promptly advanced settings request configuration http method choose the type of http request (get, post, put, patch, delete, etc ) the monitor will send headers add custom http headers to the request to simulate specific client behavior, send authentication tokens, or customize the request further request body provide the data payload for http methods that support it (e g , post, put, patch, delete) as part of the request enable basic authentication enable this option to include http basic auth credentials with the request for endpoints that require authentication follow redirects when enabled, the monitor automatically follows http redirect responses (e g , 301, 302, 307) to the final destination assertions assertions define the conditions the monitor validates against the http responses multiple assertions can be configured to ensure comprehensive monitoring status code verifies the http response status code matches the expected value (e g , 200, 404) response time measures how long the server takes to respond and ensures it is within acceptable limits header checks if specific http headers exist in the response and optionally if they match expected values body validates the response payload content by searching for specific text strings or patterns json body performs more detailed validation by inspecting parsed json elements within the response body certificate expiry (days) checks the remaining validity period of the ssl/tls certificate and alerts if it is about to expire within the specified number of days metrics metrics available to be monitored in dashboard section metric name type description labels kloudmate synthetic check http dns lookup time gauge time taken to resolve the dns for http checks check id, check name, check type, target, workspace id, location kloudmate synthetic check http content transfer time gauge time taken to transfer the content for http checks check id, check name, check type, target, workspace id, location kloudmate synthetic check http response headers size bytes gauge the size of the response headers in bytes for http checks check id, check name, check type, target, workspace id, location kloudmate synthetic check request duration gauge the total time taken for the primary operation of the check (e g , http request, dns query, grpc call) check id, check name, check type, target, workspace id, location kloudmate synthetic check connect time gauge time taken to establish a connection applicable to http, tcp, udp, websocket, and ssl checks check id, check name, check type, target, workspace id, location kloudmate synthetic check time to first byte gauge time to the first byte applicable to http, tcp, and udp checks check id, check name, check type, target, workspace id, location kloudmate synthetic check response size bytes gauge the size of the response in bytes applicable to http, tcp, and udp checks check id, check name, check type, target, workspace id, location related resources docid\ cuqd6vnjhddvn0ltauk8u