The Runscope Radar Agent bridges Runscope to private APIs not available over the public internet. By running the agent within your infrastructure, Runscope API monitors and tests can run against endpoints that are otherwise inaccessible to the cloud agents. The agent is particularly useful if you're looking to test or monitor an API in the following situations:
Use of the agent requires a trial or paid subscription.
Monitoring and testing private APIs with Runscope uses a hybrid on-premises approach. The agent runs on a host within your infrastructure but test data is managed and stored in the Runscope cloud. Using the Runscope dashboard, you have a single interface for defining tests, viewing results, configuring notifications and enabling 3rd-party integrations.
All communication from the agent to the Runscope cloud is made over outbound requests to the Runscope API via HTTPS on port 443. The agent requests work to be processed and sends back results over a TLS-encrypted connection and is not externally addressable.
Select an operating system to download the agent:
After downloading the agent, extract the executable from the .zip file and run it from your command line:
Linux and OS X
You will be prompted to sign in to your Runscope account and select a team. Once authenticated, you can save a configuration file to be used for subsequent runs of the agent (without having to sign in). To launch the agent with a specific configuration file, use the
-f command line option. This is the recommended way to start the agent. To generate a new configuration file, launch the agent without any command line options specified.
Linux and OS X
$ ./runscope-radar -f radar.conf
C:\> runscope-radar.exe -f radar.conf
With the agent running, you're now ready to use it for your tests.
After downloading and launching the agent, head over to the API test editor for the test you'd like to use the agent for. If everything is working correctly, the agent will appear as an option in the Locations section of the environment settings:
If you're testing an API across multiple realms (e.g. local, staging, prod), you may want to selectively enable the agent per-environment. The agent can also be enabled in a shared environment used across tests within a single bucket.
You can specify options on the command line to override those used in the configuration file.
||Start the agent with the configuration contained within the specified configuration file.|
||The name of the agent to be displayed in the Locations menu.|
If Runscope is unable to communicate with your agent regularly, test results that attempt to use that agent will be marked as Expired. Ensure that your agent is actively communicating with Runscope by inspecting the output of the agent. If it's unable to communicate with Runscope, verify your agent's general ability to make outbound HTTPS requests to https://api.runscope.com and https://www.runscope.com. If it is successfully communicating with Runscope, check that your API test is not mis-configured to use a disconnected remote agent with the same name. If your tests continue to expire, contact support
Need help running or configuring the Runscope Radar Agent in your infrastructure? Contact Support.