A simple example of DIY monitoring via REST APIs (Azure Monitoring).
To run, install NeoLoad. Clone this repo, then open up the AzureLoadMonitor.nlp project file in NeoLoad.
You may also use File > Import Project to bring these artifacts into another project to add on Azure monitoring to existing load test suites.
Change the following variables:
-
AzureApplicationID [Resource/Group > IAM > Service Principal > Properties > Application ID]
-
AzureClientID [Azure Active Directory > Properties > Directory ID]
-
AzureSecretKey [Azure Active Directory > App Registrations > Item > Settings > Keys > Item > Secret Key]
Add a new population using the 'AzureMonitor' User Path with 1VU constant load to your scenario, running from localhost (your controller).
Upon running, you should see Azure-related metrics available in the 'External Data' metrics tab from both the Runtime graphs editor and similarly after the test is completed in the Results.
Solution is based on: http://devchat.live/en/2017/02/27/access-metrics-using-azure-monitor-rest-api/
You may need to create/permission tokens for use in monitoring: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-create-service-principal-portal