When I think about API Analytics, I like to think about the "Goldilocks Question". This question is "Who's been using my APIs?". One of the tests of an API Analytics solution is how easy it makes it to answer this question.

In the case of the Axway/Vordel API Server's Analytics solution, you can slice the data two ways. You can:

Look at an API and see what clients are using it.

Look at a client and see what APIs they are using.

Let's look at these two scenarios. I've used a vehicle telematics scenario, where two clients ("SUV" and "Sports Car") are accessing two different APIs ("Vehicle Control API" and "Engine Metrics API").

Report of client usage per API:The screenshot below shows an API ("Vehicle Control API") during a time period: 3pm to 4pm on January 31 2013. We see the number of request to this API from each client. The client "SUV" has made 173 to the Vehicle Control API. 165 were successes. 8 were failures.

I also clicked on the "PDF" button to create a PDF of this same report. This can also be automatically generated on a regular scheduled basis and emailed.

Report per API Client:The screenshot below shows how many API requests a particular client ("SportsCar" in this case) makes to each API. In this case, it is between 3pm and 4pm on Jan 31. The client made 194 requests to the "Engine Metrics API" during this time. 192 were successes and 2 were failures.

Again, can also click on the "PDF" button to generate a PDF of this information. Or, you could schedule this PDF to be created (e.g. for the previous 24 hour period) and automatically emailed.

In this using the Axway/Vordel API Analytics, which comes with the API Server, you can answer the "Goldilocks Question" and see exactly how your APIs are being used.

About Mark O'NeillMark O'Neill is VP Innovation at Axway - API and Identity. Previously he was CTO and co-founder at Vordel, which was acquired by Axway. A regular speaker at industry conferences and a contributor to SOA World Magazine and Cloud Computing Journal, Mark holds a degree in mathematics and psychology from Trinity College Dublin and graduate qualifications in neural network programming from Oxford University.

It’s easy to fall into a pattern of dysfunctional releases, release processes that are characterized by delay, inefficiency, and endless meetings that encourage people to view releases as a problem. These are the kinds of meetings that inspire references to the movie Office Space or em...

Log data provides the most granular view into what is happening across your systems, applications, and end users. Logs can show you where the issues are in real-time, and provide a historical trending view over time. Logs give you the whole picture.
Logstash is an open source tool fo...

Over on the other side of the fence IT ops are screaming at the various portfolio dev teams for releasing highly risky functionality way too frequently but since the Agile dev adoption production has only had a couple of low priority P4 incidents caused by bad code releases. Things mus...

Application experience aficionados take note: you have choices now. No longer are you constrained to just HTTP/1 with a side option of WebSockets or SPDY. HTTP/2 is also an option, one that like its SPDY...

When it comes to finding useful articles, news and general information in the DevOps, CD or Agile industry, LinkedIn is usually the ticket.
We all know LinkedIn is a great tool for networking and connecting with friends, but it has also turned out to be a tool used to start meaningf...