Backup Private Locations
Specific scenario that I'm curious about. If I have a monitor running on a private location, and that location for some reason goes down so that I'm unable to run any monitors on it. Is it possible to set another private location as a backup so that if the monitor's primary location goes down, the monitor can still run and alert on the backup? I know there is an option to have monitors run on multiple locations either at the same time or through a rotation, however, I would only want the monitor to run on the backup location if the primary location is unavailable.
Set Primary Location via API
I am trying to add a list of monitors using the API, I have all the necessary JSON field names, but I am getting an error that the "Primary location X is not in the listed locations home_location". I have set home_location to the id of our private node servers using both the text and number. Also The error "Primary location X, the X is not the correct number of the location when getting the location via API, I didn't know if the X is an error. Just a note I did try the location that was shown in the error, but still get the error. I can click in the GUI on the private node and set the primary location ok, just not via the API. I just need to know if this can be done via API, what is the correct JSON field name and what location number I should use or is the only choice that will I have to click through my list of sites after the monitors are created. Also I could be overlooking this, but what is the JSON field name used to set up alert recipient groups? If this can't be done via API is there a way to set it for a group of monitors all at once? Thanks for your helpAlertSite Deployment Notice
The following updates were deployed on 4/30/2019: You may now include private locations in your default location configuration. This will be useful for customers with many private locations who wish to limit the default location spread for new monitors. As part of this change, we've renamed the Public Locations to Default Locations. This screen can be accessed at Settings>Default Locations. Various bug fixes and performance enhancements have also been deployed. To read more about AlertSite Locations, click here.Important Monitoring Location IP Address Update
Some location updates for you: Two additional nodes have been added to our London, UK - Docklands location with the following IP addresses: 31.132.1.2 78.110.160.10 Two additional nodes have been added to our Birmingham, UK location with the following IP addresses: 212.84.89.160 212.84.89.155 A new node will be added to our Seattle location on 12/5/2018 with the following IP address: 70.42.161.88 Latest location info can be found here!PrivateNode Connectivity Alerting!
We've rolled out integrated connectivity alerting to let you know when a PrivateNode has stopped communicating to the AlertSite platform. These alerts are critical to letting you know when a PrivateNode has been shut down unexpectedly or when it can no longer communicate with the AlertSite platform. These new alerts are configured via the Private Location settings screen in the UXM console and do not require additional components to be added to the actual Private Node (such as the Server Agent module). This first release supports all PrivateNode Server versions, including InSite hardware appliances and all VM versions. Support for PrivateNode EndPoint will be released later this year. Read more here!AlertSite Hurricane Florence Preparedness Statement
As you probably know, a major hurricane is set to strike North Carolina in the US Southeast. Be advised that the core AlertSite platform runs on a highly available cloud infrastructure featuring failover and disaster recovery capabilities. Furthermore, AlertSite monitoring locations function independently from the core platform and will continue monitoring and alerting in the event of a disruption to SaaS platform. In the case of Hurricane Florence specifically, it may be prudent to temporarily modify the primary location for monitors configured to use Charlotte, NC as primary.
