The smoking gun – when an API goes bad.
Many of our clients use our product just for monitoring the uptime of an API. But our data retention policy, and our analysis tools, add a whole important layer to the value APIContext brings to operations management – both from a management overview approach with our CASC scoring, and for developer operations with our detailed analysis.
One client, an organization with a number of branches and a requirement to provide those details publicly, had realized – both with our product and others – that one of their critical APIs had dramatically slowed down. It went from sub 500ms per call to more than 10,000ms. (That’s TEN SECONDS to the rest of us.)
They were really struggling with when the call went wrong: While they had APIContext monitoring uptime, they hadn’t thought to look at the latency responses in our product.
When they did take a look, they were able to see instantly that a software update to the API platform on June 8th was the likely culprit. They could actually identify the point at which the update was applied. In the meantime, months had been wasted trying to figure out what had happened – and their other products hadn’t stored logs long enough ,or with enough focus on the end user, to understand the issue for their APIs.
Don’t waste time and money on internal fights or disputes with clients. APIContext gives you the data to spot problems when they occur – and fix them before even your customers notice.
