There are a variety of ways to get API requests and responses into your Traffic Inspector buckets to view, share, search and alert on.
The most common way to collect traffic is the high-performance Global Traffic Gateway. When using the gateway, traffic is automatically routed to the nearest service region to minimize travel time. The gateway network also automatically routes around any service availability issues in specific regions to maximize uptime.
If the API calls you'd like to watch are on a private network, traffic can be collected with the on-premises Gateway Agent.
The Runscope API allows you to ingest data from other sources like an API management tool, service or proxy. Requests created via the Messages resource are evaluated as they are added. Requests matching your alert criteria will generate notifications.
Request captures are 'one-way' requests made to an endpoint for logging and inspection, generally for debugging webhooks or client requests before relaying them to an upstream API.
The Runscope Kong plugin will store requests made through your Kong gateway in the Runscope Traffic Inspector for viewing, searching and sharing. You can also create Live Traffic Alerts to receive notifications for specific request or response conditions.
The Traffic Inspector works with any HTTP client library in any language or framework by using a Gateway URL in your code. Here are some examples using popular HTTP clients with Gateway URLs in your code.
Because Runscope only requires you to update the URL, using a library isn't strictly necessary. But it can be convenient. Here are some official and community-contributed libraries that make creating Gateway URLs a breeze.