About Paul Cray

This author has not yet filled in any details.
So far Paul Cray has created 41 blog entries.

Everything You Need to Know About the APImetrics CASC Score

One of the things about APIs is that they're complicated. There's a lot of things that can and do wrong. So there are many metrics that we measure for each API. That's why we came up with the CASC Score as part of our APImetrics Insights analytics package. CASC stands for Cloud API Service Consistency. But what is a CASC Score? Simply put, you don't want to know just that your API is performing. You also want to know HOW it is performing. Our CASC Score is a number between 0 and 1000 that tells you how well an API [...]

By | April 21st, 2017|Summary, Support|0 Comments

Our Global API Economy: The Importance of API Metrics

We are living in an API economy. Organizations of every kind depend on APIs to exchange mission-critical, time-sensitive data and information with customers, suppliers, partners and other stakeholders. Given the importance of APIs to modern businesses, API metrics must be measured and managed. For example, you need to know what's happening on a minute-by-minute basis on Cyber Monday. But you also want to know whether anyone is actually using that API that DevOps spend so much time, effort and money building. "Always returning 200!" says DevOps Server, load balancer and gateway logs can tell you something about your API metrics. [...]

By | April 18th, 2017|Opinion, Summary|0 Comments

Census Data #API is Down

The US Census Bureau tweeted this about their API on the morning of Apr 6, 2017. They even sent us an email: We are currently experiencing an extended interruption in service for the Census data API. We are working to resolve the issue and apologize for any inconvenience. And indeed, there has been an extended interruption. As part of our efforts here at APImetrics to understand the global API ecosystem, we monitor hundreds of public APIs. These include two US Census Bureau APIs – the populations of California in 2010 and King County, WA in 2010. Both of these APIs [...]

By | April 7th, 2017|Government, News, Sectors, Summary|0 Comments

“No problem. We’ll write a cURL script to do that”

Does this story sound familiar? Marketing's having an issue with a mission-critical API. DevOps says there is no issue. After much research, Marketing was right – there is a problem. The API doesn't always return the expected fields, and sometimes it takes so long to respond that the user app times out. Is there any way to monitor the API and see if there is an issue? "No problem," says DevOps. "We'll write a cURL script to do that." So someone in DevOps is assigned the task. It'll only take a few minutes. OK, it took a few hours in [...]

By | April 5th, 2017|Case Studies|0 Comments

That 3AM Call

It's 3 a.m. You're dead asleep. The phone rings. You blunder around trying to locate your phone. Oh thank God - it's work! Only work. No one is dead. It's the support desk. Your most important customer's service has gone down. It might be the middle of the night where you are, but not where your customer is. If their service is down, it means they're losing revenue – and if they're pointing the finger at you, your company is going to be in a whole heap of pain. "It's OK," says the DevOps guy a couple of minutes later, [...]

By | March 30th, 2017|Opinion|1 Comment

Your APIs are Only as Good as the APIs They Depend On

On February 28, it seemed like half the internet went down. The Amazon AWS S3 cloud storage system in northern Virginia suffered an outage that lasted more than four hours. In internet time, that’s an eternity – and potentially a lot of lost revenue for Amazon and its customers. The same goes for all the hair-on-fire in operations and support, and the ripples of disruption spreading down the line to end users. If you rely on a third-party service like Amazon AWS S3 to provide mission-critical functionality, your clients are going to blame you when it goes down. AWS is [...]

By | March 22nd, 2017|Cloud, IT and Cloud, Opinion|0 Comments

Tesla’s API outage is a lesson for everybody in today’s hyper-connected world

Forty years ago, the average car barely had a transistor in it. But a car in 2017 is basically a bunch of incredibly sophisticated software riding around on some very high-end processors attached to a chassis. Sometimes you can’t even open the doors if the car app can't access to the manufacturer’s API.  Outraged Tesla owners discovered this during its 20-hour outage last week. Tesla relies on constant communication between the company’s data centers and its vehicles. This gives them vital real-time information to manage the cars safely, optimize their performance and, in some circumstances, simply make the cars go. [...]

By | March 15th, 2017|Case Studies, News|0 Comments

The Internet is Coming for your Things

The Internet of Things (IoT) has gone from a “buzzword” term, to a potential multi trillion dollar industry. No longer is the idea of a “smart home” or connected self-driving cars a science fiction fantasy, but rather a near future reality. The first IoT device was a Toaster created by John Romkey in 1990. The Toaster was connected to a computer with TCP/IP networking. It then used an information base (SNMP MIB) to turn the power on. 25 years later, there are nearly 2 billion smartphone users in the world (Source), and the number of other connected devices grows daily. [...]

By | August 5th, 2015|Opinion|2 Comments

Tracking API Calls with APImetrics

Using APImetrics to provide easy to track calls. We already provide logs of all API calls that include a detailed time stamp so you can find a specific item. Here’s another way to track calls through your entire stack: add a header to each test using the unique result or workflow result ID. In the API Call edit view, add a Header. Set the key name to something, such as X-APImetrics-ID and set the value to %%RESULT_ID%%. If you’re running the call as part of Workflow, you could also add a Header with %%TEST_RUN_RESULT_ID%% which would be the same value [...]

By | July 29th, 2015|Feature updates|0 Comments

API Documentation Needs Love too

At APImetrics, we mainly deal in the analytics of APIs and the corresponding infrastructure that supports them. These traits are easily quantifiable and the results make for simple benchmarking and examination. Another crucial, yet slightly ambiguous attribute is the API’s documentaion. Developers spend countless hours designing and building the APIs that users depend on and love, but they tend to take shortcuts when it comes to documenting. It is easy to argue that the most important piece of UX for this type of product is not actually the Sign-Up, Homepage, or even the SDK download page, but actually the Documentation. [...]

By | July 22nd, 2015|Opinion|2 Comments