Runscope API Monitoring    Learn More →

3 Reasons Your API Might Fail

3 Reasons Your API Might Fail

By Michael Churchman on .

APIs. You depend on them, but can you always trust them to work as advertised? The truth is that APIs can fail, and even when they don't fail, they can perform in ways that are less than adequate. When that happens, your application may be left hanging, or worse yet, it may crash. What kind of failures are we talking about, and what can you do about them?

First, though, consider what an API does—It provides a way for a programmer to communicate with an external application or service, and to ask that application to do something. You may or may not know what the other program does internally with your data and your request, but as long as everything works correctly, all you need to know is how to use the API. But that is not enough to ensure that APIs perform adequately.

In this article, we'll look at three common reasons why an API might fail or underperform, and how DevOps engineers can address them. [...]

Read More →

Categories: apis, debugging


What's in a Modern Software Monitoring Toolkit?

What's in a Modern Software Monitoring Toolkit?

By Twain Taylor on .

As the application stack moves from hardware-centric to cloud-centric and now to container-centric infrastructure, much is changing. Processing power is on the rise with more powerful compute instances like GPUs becoming more accessible, and compute and data storage costs are on the decline as the cloud makes resources cheaper. The application stack is becoming more complex and dynamic. With all these changes, monitoring has become more important than ever. The only way to operate in a world of distributed apps, teams, infrastructure, and cloud tooling is to monitor the entire stack end-to-end.

Monitoring used to be limited to a single tool like Nagios. These tools monitored closed systems with components that don't change regularly, and with relatively few metrics to keep track of. Then came tools like New Relic which covered application performance. Slowly, as more tools were added to the mix, monitoring was taking on a best-of-breed approach. Integrations were becoming important as data is more valuable when viewed in different contexts and using multiple tools. And then Docker happened, and the world of software delivery has never been the same.

Let's look at the various types of monitoring tools required to gain visibility [...]

Read More →

Categories: monitoring, microservices


Tutorial: Integrating Runscope with CA APM

Tutorial: Integrating Runscope with CA APM

By Heitor Tashiro Sergent on .

Note: We'll be at AWS Summit San Francisco on April 4th! We'll have our own little booth there, so if you can please come and find us (the event is free!) and we'd love to chat with you. :)

CA APM is an Application Performance Management solution that can help teams gain performance insights and diagnose issues across the full software lifecycle. It includes transaction tracing that supports modern APIs and apps, and it can help teams get to the root cause of bugs in APIs, transactions, code and database calls.

By connecting CA APM with Runscope API monitoring, you can get a complete picture of your application and find the root cause of why an API is slow or failing.

Watch the following video to learn how...

Read More →

Categories: tutorial, product, integrations


10 Steps to a Painless API Release

10 Steps to a Painless API Release

By James Higginbotham on .

James Higginbotham, Executive API Consultant, shares his API and product release insights with a list of 10 essential steps to improve the next release of your API.

If you're interested in being a part of our next series, fill out this short form and we'll get in touch with you for our next run.

It is exciting to release something new. The thrill of seeing an idea to completion is always an exciting time for software teams. But how do you know when an API is ready to release? What if you missed something that could result in increased support emails and calls? What if you broke existing internal or 3rd-party integrations?

This article provides a 10-point checklist to help ensure your next API release is as smooth as possible.

1. Did you verify that we met stakeholder needs?

You may design the most beautiful, amazing API ever imagined. It might cause API designers to weep at its beauty. But, if it doesn't solve the problems of your stakeholders, you have failed to deliver a well-designed and useful API. [...]

Read More →

Categories: apis, community, featured guest series, openapi


Phasing out the Traffic Inspector

By John Sheehan on .

tl;dr -- The Runscope Traffic Inspector, including the traffic gateways, request captures, collections, shared requests, live traffic alerts, on-premises gateway agent are being phased out over the next 180 days.

Runscope API monitoring features are not affected by this shut down. All monitoring functionality (API tests, on-prem Radar agent, schedules, global test locations, notifications, etc.) will continue to operate normally.

Shutting down a product is always a tough decision. However, our customers have overwhelmingly demonstrated to us that API monitoring is where they get the most value out of Runscope. In a given month, ~90-95% of customer usage of our products is focused on API monitoring. While the Traffic Inspector has utility, its utilization does not justify the investment of resources required to keep it running. By focusing on a single product, we'll be able to more intently build the most reliable and secure API monitoring tools for our customers. [...]

Read More →

Categories: announcements, product


Everything is going to be 200 OK®