These Advanced Actions allows you to integrate with Azure in order to correlate data from one tool to another.

This bundle provides inbound integration:

• AzureMonitoring
  • Azure Application Insights → NeoLoad: Retrieves infrastructure and service metrics from Azure Applicaiton Insights and inserts them in NeoLoad External Data so that you can correlate NeoLoad and Azure Application Insights metrics within NeoLoad.

1. Download the latest release for NeoLoad from version 7.0
2. Read the NeoLoad documentation to see How to install a custom Advanced Action.

Once installed, how to use in a given NeoLoad project:

1. Create a “Azure Insights” User Path.
2. Insert "AzureMonitoring" in the ‘Actions’ block.

   

3. Configure "AzureMonitoring" by specifying your application ID and API KEY

   

4. Select the Actions container and set a pacing duration of 30 seconds.
5. Create a "PopulationAzure" Population that contains 100% of "AzureMonitoring" User Path.

   

6. In the Runtime section, select your scenario, select the "PopulationAzure" population and define a constant load of 1 user for the full duration of the load test.

   

7. Do not use multiple load generators. Good practice should be to keep only the local one.

You need the Application ID and an API Key to access Application Insights through the API. To get these two keys:

1. In Azure portal, open the Application Insights resource for your application and open Settings, API Access.
2. The Application ID is a unique, unchangeable identifier for this application.
3. Create a new API key, checking the "Read telemetry" box.
4. Copy the key before closing the Create API key blade and save it somewhere secure. (If you lose the key, you'll need to create another.)

Tip: Get NeoLoad API information in NeoLoad preferences: Project Preferences / REST API.

This bundle does not work with the Check User Path mode. A Bad context error should be raised.

• Azure monitoring
  • NL-AZURE MONITORING_ACTION-01: Could not parse arguments
  • NL-AZURE MONITORING_ACTION-02: Technical Error
  • NL-AZURE MONITORING_ACTION-03: Bad context