In the Runtime section, select your scenario, select the "PopulationNewRelic" population and define a constant load of 1 user for the full duration of the load test.ĭo not use multiple load generators.Create a Population "PopulationNewRelic" which contains 100% of User Path "New Relic".Select the Actions container and set the runtime parameters "Reset user session and emulate new browser between each iteration" to "No".Select the Actions container and set a pacing duration of 60 seconds.Insert Custom action "New Relic Monitoring" in the Actions container (custom action is inside Advanced > APM > New Relic).
#Neoload pulling data from a table how to
Once installed, how to use in a given NeoLoad project:
#Neoload pulling data from a table install
Outbound (NeoLoad Web → New Relic): With load testing data in New Relic, a tester can build complex dashboards correlating several types of metrics.Since NeoLoad GUI 6.8 version, these metrics are sent to NeoLoad Web.
This allows the correlation of load performance and APM results from the NeoLoad's Dashboards. Inbound (New Relic → NeoLoad): Retrieves metrics of the SUT from New Relic and injects them in NeoLoad Controller through the Data Exchange API.
This bundle provides both an inbound and an outbound integration: This Advanced Action allows you to integrate NeoLoad with New Relic in order to correlate data from one tool to another. New Relic Integration for NeoLoad Overview
0 kommentar(er)
