This showcase demonstrates how the combination of Dynatrace and LoadView will close remaining gaps in the performance engineering chain.
Shanghai, China – May 28, 2013 – Dotcom-Monitor has made an emergency update to its Shanghai, China location, due to telecom routing issues. Current Dotcom-Monitor clients who filter monitoring IP addresses should note the change, effective immediately.
The new Shanghai, China Network Location IP Address is 220.127.116.11
Dotcom-Monitor has launched a new script playback feature to the EveryStep Scripting Tool. EveryStep is the website scripting tool that records a script on a website with simple point and click actions. With the new feature, now you can record a script and schedule it to run automatically on your desktop and send you alerts if it detects any errors.
For example, open the EveryStep scripting tool, click record and navigate through an e-commerce website adding items to your shopping cart and confirming the checkout process, recording the path to purchase. After recording your script you can replay it on your desktop to ensure that everything was recorded properly and edit the script to fix any errors or add necessary elements.
User Interface Update:
There are several exciting new features along with some updated cosmetic changes to the Dotcom-Monitor user interface.
Here is a brief overview of the changes:
The color scheme has been updated to make the site easier to read.
On the Device Manager (The first page you see when you log in), you can now see the details of the packages you have purchased, including the maximum monitoring frequency and # tasks available / total tasks purchased.
The Device Manager now displays DOWN when the status of a device is down based upon the schedules and filters you have applied to the device
The new DNS caching features at Dotcom-Monitor allow you to perform some interesting tests that show how DNS caching can affect your page load speed.
We realize that many organizations monitor their online services with a number different goals in mind, and so we listened to the feedback we received that some users want to include the DNS response time in their monitoring and some users want to be able to remove DNS response from their monitors.
How you wish to handle DNS response time in regard to your monitoring needs is up to you, but we want to take this opportunity to show the differences in how DNS response time affects website load using our new tools.
We ran a test monitoring YouTube from a single location in the midwest United States with three different DNS cache settings. A basic HTTP full page load on the YouTube front page resulted in some interesting, although not that surprising results.
Keep in mind the results will vary depending upon a number of variables such as which locations you are monitoring from, the time of day, the load on the DNS servers, and on the website servers.