CloudMonix allows for basic monitoring of Websites (URLs). URL monitoring allows an external monitoring of public websites and is a last-resort check on the health of a system.
CloudMonix supports a wide variety of settings that users can tweak, to customize how CloudMonix connects to monitored URL.
|Timeout||Timeout in milliseconds, after which CloudMonix will mark the state of the website as Down|
|Retries||Number of times CloudMonix will retry pinging a website if it times out, before marking the state of the website as Down|
|Method||Web method that should be used to ping the website. Certain URLs may report a POST or a PUT instead of traditional GET|
|Content Type||Certain URLs may require or depend on content type to be defined before a request is made|
|User Agent||Certain URLs may require a specific User Agent to work properly. If user agent is not specified, default "cloudmonix-bot" agent ill be used|
|Credentials||CloudMonix can supply BasicAuth or Windows (NTLM) based credentials for secure URLs if they require it|
|Headers||CloudMonix can supply custom headers if needed by the monitored URL|
|SSL errors||CloudMonix can ignore SSL certificate errors if the monitored URL is using a self-signed or otherwise invalid certificate|
In addition to URL-specific metrics that CloudMonix can track when monitoring a particular URL, CloudMonix can always track Linked and Aggregate metrics. Linked metrics allow for consumption of another resource's metrics alongside the monitored URL in order to be able to holistically evaluate conditions across multiple resources. Aggregate metric can be used to monitor trends in performance. It is possible to track such metrics as average ResponseTime for the last 30minutes, etc.
|ResourceStatus||string||Metric that identifies the last state of the monitored website. Possible values are: Ready, Down, or Unknown. Website is marked down when it responds with an error or does not respond within specified timeout for number of times specified the by the Retries setting. This metric is often used to evaluate outage criteria of the monitored resource.|
|UrlResponseCode||int||Metric that identifies the last HTTP response code of the monitored website (ie: 500, 404, 200, etc)|
|UrlResponseText||string||Metric that tracks text (usually HTML) response from the monitored website. Avoid tracking this metric for websites that return a lot of content, to ensure that monitoring cycles for your particular website do not slow down due to sheer volume. Capture of this metric is often useful for trying to ensure that particular keywords exist in the HTML of the monitored website.|
|ResponseTime||decimal||Metric that tracks the time in milliseconds that the website took to respond to last monitored request.|
|UrlSslExpirationInDays||int||Metric that tracks the number of days before SSL certificate presented by the monitored website, expires (this metric only applies to secure https websites)|
When particular conditions arise, it maybe necessary to instrument a POST or other web action against a monitored URL. This provides ability for CloudMonix users to instrument a very particular custom action when specific monitoring conditions occur.
Web Request against a monitored URL can be performed with specific JSON payload.
Web Request against a monitored URL can be performed with specific XML payload.