How to configure Blazemeter and Dynatrace.
Release : SAAS
Component : BLAZEMETER PERFORMANCE TESTING
A Dynatrace API is required when integrating with BlazeMeter. To create the API v1 login to Dynatrace and navigate to the following location:
Settings / Integration / Dynatrace API
Click on the button “Generate Token”
Enter a name for the token and select the entire scope for API v1, then click Generate:
Make a copy of the token and save this for later use:
Login to Blazemeter and navigate to the “Settings” / “Credentials” screen and click on the blue plus button to add a new credential.
Click on dynatrace button:
Name the new credential and enter the URL for the Dynatrace server and the API v1 token that was previously generated. NOTE: Verify the URL does not have a forward slash (/) at the end.
If the Dynatrace server is SaaS the Harbour ID can be left empty but when using an on premise Dynatrace server you must enter the Harbour ID for the On Premise Location (OPL) that has been deployed on a network that can access the dynatrace server (i.e inside the firewall)
To include the Dynatrace metrics in a performance test navigate to the APM Integration section of the test and select “Dynatrace APM” from the using the blue plus sign button:
Select the Dynatrace credentials that were previously created and click Next:
Select the Entity type that is required for the Dynatrace Profile:
Select all of the Metrics that are required and when the list is complete click next:
Enter a name for the profile and click Save:
Click Apply to add the profile to the test:
The Profile is now associated with the test:
The integration between BLazeMeter and Dynatrace is accomplished by making API calls from BlazeMeter to your configured Dynatrace APM instance (URL) through the DynaTrace API token you have configured in the integration.
To help to troubleshoot why you are unable to pull metrics from the Dynatrace APM you have configured in your test, you need to try running a curl command from a shell in the crane Docker container on the OPL where you will run this test.
Here are the steps to do this:
Once you have the container ID of the crane container on your Private Location, the correct docker command to start a shell in that container is as follows:
docker exec -it <crane container id> /bin/sh
Check to see if curl is installed in that container once you have started up a shell by using the following command:
If it fails with an error like "command not found", then try installing curl using the following command:
apk add curl
Verify that curl has been installed in the container:
If it has, then you can run the curl command suggested to verify that you have access to the Dynatrace APM using the Profile API token you have configured in your integration:
curl -L -X GET 'https://<Dynatrace APM URL>/api/v1/timeseries' -H 'Authorization: Api-Token <Dynatrace Profile API v1 token>'
If this curl command fails on your OPL, then you need to look into what is preventing you from accessing the Dynatrace APM APIs from the OPL. It may be a firewall rule that is blocking access to the configured Dynatrace APM URL or it may be a permission issue for the Dynatrace Profile associated with the API token configured (see the Token scopes section of the Access tokens Dynatrace page for more information on these permissions).