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 →
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 →
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 →
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 →
Runscope has a number of different integrations that allow you to leverage other tools in conjunction with your Runscope API monitors. However, for tools that are not included in our list of built-in integrations, we allow you to use Webhook notifications to automate your process. Webhook notifications are POST requests that are made at the completion of a test, and include a payload with details about the test run.
Runscope has two options for webhooks:
- Basic Webhooks: fired on completion of every test run. They can be activated in your test environment settings -> Webhooks.
- Custom Webhooks: you can specify failure only for a threshold of consecutive failures (3, for example) before sending the POST request. They can be added by going to Connected Services and setting the required parameters, and then activated in your test environment settings -> Integrations.
Either way, Runscope makes it easy for you to build your own integrations. However, receiving a webhook requires some piece of infrastructure that will receive and process the POST request, and some customers might not have their own infrastructure readily available, or the resources to create custom endpoints.
In this blog post, I’m going to walk through using Google Sheets as a quick alternative to listen for webhook notifications. [...]
Read More →
Security is a top priority for us at Runscope. It's important for us to make sure that your data is always safe, and to also empower you with any tools that we can to allow you to protect your companies' data.
We added support for two-factor authentication back in July of 2015. Users could enable 2FA in their accounts via SMS, or by using the Authy app. But, we understand that sometimes users can have different apps that handle 2FA, such as Google Authenticator and other TOTP compliant apps that require a QR code.
So, last week we've added support for Google Authenticator and other apps as two-factor authentication options for Runscope users! [...]
Read More →