You can think of response time as a service-level agreement (SLA) for
your users. Here’s how to test it with Loader and New Relic Insights.
You can have your test results pushed in real-time to New Relic Insights.
Click on your account name on the top-right, and then click Integrations:
Choose New Relic Insights tab and specify your New Relic Account ID and your New Relic Insights Key:
Once you have saved your New Relic Insights credentials in the integration page, loader.io will automatically send data to New Relic in real-time whenever you run a test.
The data sent to New Relic Insights has type "loaderio". It contains the following fields for each time interval:
|avg_time||Average response time (ms)|
|clients||Number of clients|
|data_in||Data transferred into web application (cumulative)|
|data_out||Data transferred out of web application (cumulative)|
|forbidden||Number of requests against domains that were not validated|
|max_time||Slowest response (ms)|
|min_time||Fastest response (ms)|
|other_errors||Errors other than 400s, 500s, or timeouts|
|requests||Number of requests|
|resp_1xx||Number of HTTP server response codes between 100-199|
|resp_2xx||Number of HTTP server response codes between 200-299|
|resp_3xx||Number of HTTP server response codes between 300-399|
|resp_4xx||Number of HTTP server response codes between 400-499|
|resp_5xx||Number of HTTP server response codes between 500-599|
|timeout_errors||Number of requests that timed out waiting for a response|
Note that these values are summed over all of the URLs in a test. For example, if you have three URLs in a test, then
avg_time refers to the sum of the average response times of all three URLs in that time interval.
You can use this data in your NRQL queries. For example, to do a timeseries plot of average response time for the last 5 minutes at 1 second intervals, you would do:
SELECT average(avg_time) from loaderio since 5 minutes ago TIMESERIES 1 second
The output would look something like this: