Additional data points for "Transaction Step Summary" Report
We will gain more insights if we have the below additional options in"Transaction Step Summary" Report: 1) Have the option to select multiple locations 2) Ability to provide the data at granular level rather than the aggregated level (Example: If we are running the report for last last 7 days or last 1 month, we are seeing in this report, only one data point per transaction step per day which is the aggregated/consolidated value; we want to have the option to view individual data points per script run also in this report)
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 helpImportant AlertSite Monitoring Network Upgrade Notice
Dear AlertSite Customer, I’m excited to tell you about updates we’ll be making to our monitoring network in the next few months. We will be updating the browser versions for all three DejaClick playback options. First up will be Firefox, which will be upgraded from v38 to v52. This update will roll out to our public monitoring network in January of 2018. We will also be updating Firefox to v52 for PrivateNode Server v2.1 and greater* and this update will likely arrive in late January. Our Internet Explorer locations will moving from IE9 to IE11. This update should be complete in February 2018. There is also a likelihood that some location changes my accompany this version upgrade. Stay tuned for more details. Last, but not least, Chrome will be upgrading from v47 to (most likely) v64 (depending on the timing of our final QA, the exact version might swing to v63 or v65). We are targeting February 2018 for this upgrade and will communicate more specific timeframes as soon as possible. As with Firefox, this upgraded Chrome version will also be included in a PrivateNode update for PrivateNode Server v2.1 and greater* in the same general timeframe as the public location rollout. We will keep you in the loop as these rollouts progress. If you have any questions, please feel free to ask via comments or reach out to me or your customer success manager. * if your PrivateNode Servers (or InSites) are on a version prior to 2.1, please contact your CSM to learn about upgrade options Thanks and Happy New Year! Denis Goodwin Director Product Management, AlertSite
