API Time Travel

API Time Travel

We frequently check general performance data to look for ‘odd’ responses and we found an interesting one today which involved an API call on a test server which took -284,027ms, or just a little under 5 minutes.  We assume that the host had to have a clock reset in the middle of making the API call, but it was an interesting results and one which has led to a small change on our side to error out such platform induced time issues in the future.

Once again, this makes it clear to us that just ‘assuming’ that the cloud is there and working for you is a dangerous assumption that that many, many things can impact end user performance and monitoring and tracking is an essential part of the mix.

If you are not already using us, why not try us out?