This integration is not supported anymore because all the features are natively available into Neoload 7.5 and above.
No more updates will be published on this repository. The experimental version still propose a "Sanity Check" to validate the right deployment of a new release, for example. This is the only feature that is not included in Neoload.
| Property | Value |
|---|---|
| Maturity | Deprecated |
| Author | Neotys Partner Team |
| License | BSD Simplified |
These Advanced Actions allows you to integrate NeoLoad with Dynatrace in order to correlate data from one tool to another.
This bundle provides inbound and an outbound integration:
-
DynatraceEvents: Links a load testing event to all services used by an application monitored by Dynatrace. Data sent: Neoload Project, Test and Scenario Name. NeoLoadWeb Frontend Url.
-
DynatraceMonitoring
-
Dynatrace → NeoLoad: Retrieves infrastructure and service metrics from Dynatrace and inserts them in NeoLoad External Data so that you can correlate NeoLoad and Dynatrace metrics within NeoLoad. Since NeoLoad GUI 6.8 version, these metrics are sent to NeoLoad Web.
-
Infrastructure metrics:
host.availability, host.cpu.idle, host.cpu.iowait, host.cpu.steal, host.cpu.system, host.cpu.user, host.disk.availablespace, host.disk.bytesread, host.disk.byteswritten, host.disk.freespacepercentage, host.disk.queuelength, host.disk.readoperations, host.disk.readtime, host.disk.usedspace, host.disk.writeoperations, host.disk.writetime, host.mem.available, host.mem.availablepercentage, host.mem.pagefaults, host.mem.used, host.nic.bytesreceived, host.nic.bytessent, host.nic.packetsreceived
-
Service metrics:
service.clientsidefailurerate, service.errorcounthttp4xx, service.errorcounthttp5xx, service.failurerate, service.requestspermin, service.responsetime, service.serversidefailurerate
-
-
NeoLoad -> Dynatrace: Sends the global statistics of the test to Dynatrace OneAgent so they can be used as custom metrics in Dynatrace dashboards.
- Custom metrics:
Request.duration, Request.Count, Transaction.Average.Duration, User.Load, Count.Average.Failure, DowLoaded.Average.Bytes, Downloaded.Average.Bytes.PerSecond, Iteration.Average.Failure, Iteration.Average.Success, Request.Average.Count, Request.Average.Success, Request.Average.Failure, Request.Sucess.PerSecond, Request.Failure.PerSeconds, Transaction.Average.Failure, Iteration.Average.Success, Transaction.Failure.PerSecond, Iteration.Average.Success, Transaction.Average.Count, Failure.Rate
- Custom metrics:
-
Other experimental features in the 'develop' branch: DynatraceConfiguration, DynatraceSetAnomalieDetection, DynatraceDeleteAnomalieDetection, DynatraceSanityCheck.
-
- Download the latest release for NeoLoad from version 6.7 or this release for previous NeoLoad versions.
- Read the NeoLoad documentation to see How to install a custom Advanced Action.
Once installed, how to use in a given NeoLoad project:
- Create a “Dynatrace” User Path.
- Insert "DynatraceEvents" in the ‘End’ block.
- Insert "DynatraceMonitoring" in the ‘Actions’ block.
- Select the Actions container and set a pacing duration of 30 seconds.
- Select the Actions container and set the "Reset user session and emulate new browser between each iteration" runtime parameters to "No".
- Create a "PopulationDynatrace" Population that contains 100% of "Dynatrace" User Path.
- In the Runtime section, select your scenario, select the "PopulationDynatrace" population and define a constant load of 1 user for the full duration of the load test.
- Do not use multiple load generators. Good practice should be to keep only the local one.
- Verify that NeoLoad Web data transfer is properly configured on the Controller preferences (see Preferences / General settings / NeoLoad Web).
- Verify to have a license with "Integration & Advanced Usage".
On the Dynatrace interface
- Create (or retrieve) a Dynatrace API key from menu Settings/Intregration/Dynatrace API.
- Search for the application being tested.
- Apply a tag on the application being tested.
| Name | Description |
|---|---|
| dynatraceId | Identifier of your Dynatrace environment:
|
| dynatraceApiKey | API key of your Dynatrace account |
| tags (optional) | Dynatrace tags. Links the NeoLoad computed data to Dynatrace tags (format: tag1,tag2) |
| proxyName (Optional) | The NeoLoad proxy name to access Dynatrace |
| dynatraceManagedHostname (Optional) |
|
Tip: Get NeoLoad API information in NeoLoad preferences: Project Preferences / REST API.
| Name | Description |
|---|---|
| dynatraceId | Identifier of your Dynatrace environment:
|
| dynatraceApiKey | API key of your dynatrace account |
| tags (optional) | Dynatrace tags. Links the NeoLoad computed data to Dynatrace tags (format: tag1,tag2) |
| dynatraceManagedHostname (Optional) |
|
| dataExchangeApiUrl (Optional) | Where the DataExchange server is located. Optional, by default it is: http://${NL-ControllerIp}:7400/DataExchange/v1/Service.svc/ |
| dataExchangeApiKey (Optional) | API key of the DataExchange API |
| proxyName (Optional) | The name of the NeoLoad proxy to access to Dynatrace |
All the metrics retrieved from Dynatrace are available on the NeoLoad Controller (live during the test, and after the test is executed), in the External Data tab.
-
Find NeoLoad in Technologies.
Click on Group details:
Click on NeoLoad Data:
-
Analyze NeoLoad metrics.
Analyze all the NeoLoad metrics sent:
-
Consult NeoLoad events on the tested application.
This bundle does not work with the Check User Path mode. A Bad context error should be raised.
- Dynatrace event
- NL-DYNATRACE_EVENT_ACTION-01: Could not parse arguments
- NL-DYNATRACE_EVENT_ACTION-02: Technical Error
- NL-DYNATRACE_EVENT_ACTION-03: Bad context
- Dynatrace monitoring
- NL-DYNATRACE_MONITORING_ACTION-01: Could not parse arguments
- NL-DYNATRACE_MONITORING_ACTION-02: Technical Error
- NL-DYNATRACE_MONITORING_ACTION-03: Bad context
Learn more about the experimental features in the 'develop' branch: DynatraceConfiguration, DynatraceSetAnomalieDetection, DynatraceDeleteAnomalieDetection, DynatraceSanityCheck.