Runscope API Monitoring    Learn More →

Posts filtered by category: howto

Playing with Node.js and the Runscope API on Glitch

Playing with Node.js and the Runscope API on Glitch

By Heitor Tashiro Sergent on .

I've been wanting to create a project on Glitch for quite some time. Glitch is a startup/product/friendly community where you can create and remix Node.js projects, use an online code editor to personalize them, and you don't have to worry about hosting or deployment. And it's free! It's a really great way to start a project and prototype an idea, without having to worry about those million little things that can get in the way of your dream app.

I thought it'd be fun to share a few projects I made using the Runscope API, and how you can use them to extend Runscope functionality or create custom features for use cases you might have, like creating a custom dashboard that displays API metrics using C3.js.

Here we'll take a look at three projects:

  • runscope-oauth - Uses Passport.js + passport-oauth2 + the Runscope API authentication.
  • runscope-batch-edit - Remix of runscope-oauth, uses the Runscope API to get a list of user buckets + list of tests in a bucket + set multiple tests schedules + set multiple tests default environments.
  • runscope-api-metric - Remix of runscope-oauth, uses the Runscope API to get a test's metrics information (avg. response time, success ratio, etc.)...

Read More →

Categories: apis, code samples, howto


Debugging SSL Errors in Your API Monitoring

Debugging SSL Errors in Your API Monitoring

By Heitor Tashiro Sergent on .

When working with external or internal APIs, a million things can make it return errors: missing HTTP headers, sending an invalid authorization credential because you forgot to append "Bearer" to your API token, or even just a simple typo on the endpoint you're trying to use.

Those issues can be frustrating, and sometimes take hours of banging your head against the keyboard or reading documentation to figure out what's wrong, but the solutions are easy. Another issue that is generally much harder to fix is debugging an SSL error...

Read More →

Categories: tutorial, monitoring, howto


Tutorial: Integrating Runscope with New Relic Insights

Tutorial: Integrating Runscope with New Relic Insights

By Heitor Tashiro Sergent on .

New Relic Insights is a real-time analytics platform that collects event and metric data from other New Relic products, and also third-party integrations. By connecting New Relic Insights with Runscope API monitoring, you can collect metrics from your API tests and transform them into actionable insights about your applications.

Connecting Your Accounts

We need two get two variables from New Relic to integrate it with Runscope: an Account ID, and Insert Key...

Read More →

Categories: tutorial, monitoring, integrations, howto


Copying Runscope Environments using the Runscope API

Copying Runscope Environments using the Runscope API

By Sam Aybar on .

The Runscope UI provides a lot of flexibility for our customers to monitor and test APIs. You can easily manage the tests you have written, whether that means exporting them, duplicating them, or moving them to a different bucket.

Sometimes, however, our customers want to do something that we don’t have built-in. This is where the benefits of having a robust API come into play. For example, one customer recently expressed interest in being able to export an environment for backup purposes; another customer wanted to copy a shared environment to a different bucket.

Environments are one of the key elements in creating reusable API tests, especially when it comes to testing local, staging, and production APIs. This blog post outlines two example Python scripts to address these needs of importing/exporting environments. You can find these scripts at...

Read More →

Categories: code samples, howto, tutorial


3 Easy Steps to Cloud Operational Excellence

3 Easy Steps to Cloud Operational Excellence

By Bruce Wang on .

This is a guest post by Bruce Wang and Glen Semino from SYNQ, a video API built for developers. In this post, they explain the tools and processes they use to keep the company's API operations running smoothly, and share a real-world story of how they found an API bug before launching a new feature.

There are a lot of tools out there, and sometimes its hard to sift through them all. Here’s a simple guide to combine 3 tools, Runscope, PagerDuty and StatusPage to create a powerful cloud operational workflow that will give you peace of mind and clear visibility to your application for your customers and internal teams alike!

In case you’re not familiar with the tools, here’s a quick rundown:

  • Runscope — highly flexible API testing and monitoring service
  • PagerDuty — incident management system
  • StatusPage — Customer-facing API health status page

The workflow

It’s important to implement tools for specific purposes, and we wanted to integrate these 3 tools to help manage our operational process better. In the following examples, we’re going to show you how...

    Read More →

    Categories: apis, community, customers, debugging, howto, integrations, monitoring, tutorial


    Storing API Test Results to a Database with Eventn and Runscope

    Storing API Test Results to a Database with Eventn and Runscope

    By Eventn on .

    A common requirement for Runscope users is to save and analyze test results for alerting, building custom dashboards, and other analytical purposes. One way to do that is to pipe all your test results to an Amazon S3 bucket. But what if you want more flexibility in how you store the test results? Or if you want to filter and process the test result data before storing it? 

    Eventn is an HTTP microservices platform specifically designed for data processing and analytical workloads. You can use it to launch microservices, and each one you create provides a Node.js JavaScript function runtime that executes when an HTTP request is made.

    In this example, we will demonstrate how to call an Eventn microservice after each test completes and provide an example of saving the results to a database. We will also report on the data using SQL...

    Read More →

    Categories: howto, integrations, microservices


    Everything is going to be 200 OK®