SiteMonitors are no longer in beta and are fully supported. If you have not started taking advantage of the LogicMonitor built-in external website monitoring capabilities, consider reviewing the following section of help articles to get you started: External Website Monitoring. SiteMonitor allows you to run checks from locations in Singapore, Dublin, Los Angeles, San Francisco, and Washington DC.
If you have been whitelisting IPs to take advantage of SiteMonitor, this version (v.53) updates the IPs of the service. LogicMonitor does not suggest IP whitelisting in conjunction with the use of this feature, as the purpose is to emulate external access by your customers or affiliates to your web services.
Should you need to limit or filter connectivity, consider basing your action on the LogicMonitor user agent, LogicMonitor SiteMonitor/1.0, or creating your own custom header and custom header check for SiteMonitor use. For more information about requesting custom headers in your SiteMonitor configuration, see “Adding a Web Service Monitor” in the Help system.
- Corrects an issue in which alerts were displayed in the alert history and in the alert reports when said reports included a time period in which alerting was disabled for a particular event source.
- Resolves an issue in which the hosts tab erroneously showed some hosts or host components in an alert stage (displayed with the color red), though alerting was disabled for the object at the time.
- Corrects an issue in which the http collector did not support the POST method.
- Fixes an issue in which existing users without the default user role would be assigned the default user role during SAML-based single sign-on, even if they already had other roles in the product.
- Resolves an issue in which adding a comment to an alert in the UI resulted in an erroneous email confirming the ACK of the alert. The alert was never considered ACKed within LogicMonitor.
- Corrects an issue in which zooming on a smart graph can result in blank results, though data exists.
- Fixes a situation in which a deeper property was not being correctly inherited and set on a child of the parent but set to a property defined higher in the tree.
- Fixed an issue affecting a small number of customers where alert delivery was blocked when an external website that was an alert destination timed out.
- The Java JRE running the collector has been upgraded, for additional security. One side effect of this is that it may reject some HTTPS hosts if they use weak certificates (e.g. 768 bit keys) or ciphers.
- Updated the default communication protocol to SSL for NetApp devices on new LogicMonitor accounts.
- For each alerting session, confirming higher severity alerts applies the acknowledgement to previous the lower priority alerts which led to the higher severity. For example, ACKing a critical alert will cascade down through the warning and error level alerts, acknowledging them also.
- Full page load time is now enforced. And, alerts set on the time taken to fully load a web page will now trigger. While SiteMonitor was in beta, these settings were not enforced. Checking both Wait for all page elements to load and setting a load time in the Page load time must be less than _____ seconds is now respected and the combination will trigger alerts based on full page load time.
In this Article: