Runscope Everywhere: New Embeddable Streams and Requests

Hot off the heels of the Runscope API launch earlier this week, we bring you another way to pull and display data out of your Runscope account. This time, it's Runscope Embeddable Content, and it's awesome.

Runscope Embeddable Content gives you the ability to place stream and request detail views directly into your web site or application. These are fully-functional versions of the same stream and detail views available in our dashboard, but embeddable via some simple JavaScript calls.

There are currently three types of content that can be embedded: 

• Stream views (All Traffic, Errors, Starred, Shared, etc.)
• Private request detail
• Shared request detail

For stream views and private requests, you must first obtain an OAuth access token for the user whose data you want to embed. Shared requests don't require specific user credentials, they only require that you've already shared the message.

Let's take a look at how you can put this to use in your application. 

Example Use Case: Tracking Errors in an Internal Dashboard

Using the stream embed you can display live traffic streams from any of your buckets. You can use the default 'All Traffic' stream, or customize it to pull out one of the filtered views. Here's an example for displaying the 'Errors' stream for a given bucket which only displays 5xx-class responses and other failed requests (like connection errors). This example also includes live updating, so the stream will show new requests as they arrive in near real-time.

<script type="text/javascript" src="https://static.runscope.com/runscope.js"></script>
<script>
  var opts = {
    elementId: "errorsStream",
    clientToken: "your_token_goes_here",
    stream: "errors",
    height: 600,
    width: 960,
    updates: true
  };
  Runscope.showStream(opts);
</script>

<div id="errorsStream"></div>

Get Started

Head over to the Runscope Embeddable Content docs to get all the nitty gritty details for how it works. Pay special attention to the client token docs since it's an important part of getting embeds working for the stream and private message views. As always, if you run into any problems or have any questions, we're standing by.