Neotys

The integration of Dynatrace with Neotys is fully automated and enables faster test design, execution, and analysis. Neotys and Dynatrace data is combined and can be viewed in the Neotys dashboard, thereby allowing for automated root cause analysis and multi-dimensional diagnostics.

DynatraceEvents: Links a load testing event to all the services used by an application monitored by Dynatrace and sends the following data: 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. In NeoLoad GUI version 6.8 and later, 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, pgi.cpu.usage, pgi.jvm.committedmemory, pgi.jvm.garbagecollectioncount, pgi.jvm.garbagecollectiontime, pgi.jvm.threadcount, pgi.jvm.usedmemory, pgi.mem.usage, pgi.nic.bytesreceived,
pgi.nic.bytessent`

Service metrics:

`service.clientsidefailurerate, service.errorcounthttp4xx, service.errorcounthttp5xx, service.failurerate, service.requestspermin, service.responsetime, service.serversidefailurerate`

DynatraceMonitoring - Neoload > Dynatrace: Sends the global statistics of the test to Dynatrace so that 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

Installation

Download the latest release of the Dynatrace integration for Neotys. For releases prior to 6.7, download this version.
Take a look at the NeoLoad documentation for installing a custom Advanced Action.

Set up NeoLoad

Create the Dynatrace user path.
Insert DynaEvents in the End block.
Insert DynatraceMonitoring in the Actions block.
Select the Actions container and set the pacing duration to 30 seconds.
Select the Actions container and set Reset user session and emulate new browser between each iteration to No.
Create a PopulationDynatrace population that contains 100% of the Dynatrace user path.
Under Runtime Scenarios, select the scenario, select PopulationDynatrace, and define a constant load of 1 user for the full duration of the load test.

Note: Don't use multiple load generators.
Go to Preferences > General settings > NeoLoad Web and verify that the NeoLoad Web data transfer has been correctly configured.
Verify the license under Integration and Advanced Usage.

Set up Dynatrace

From the Dynatrace UI, go to Settings > Integration > Dynatrace API to create a Dynatrace API key.
Under Transactions & services, apply the correct tags to filter and list all Neotys monitored applications.
Add a tag to the application that is being tested.

Dynatrace events

Parameters

Name	Description
dynatraceId	In live environments, the identifier is part of the URL. In Dynatrace Managed, the identifier is the UUID
dynatraceApiKey	Key to the Dynatrace account
Optional tag	Dynatrace tags to link to the NeoLoad computed data
Optional proxyName	NeoLoad proxy name to access Dynatrace
Optional dynatraceManagedHostname	The hostname of Dynatrace Managed environments. Not applicable to live environments.

Status codes

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

Parameters

Name	Description
dynatraceId	In live environments, the identifier is part of the URL. In Dynatrace Managed, the identifier is the UUID
dynatraceApiKey	Key to the Dynatrace account
Optional tag	Dynatrace tag to link to the NeoLoad computed data
Optional proxyName	NeoLoad proxy name to access Dynatrace
Optional dynatraceManagedHostname	The hostname of Managed environments. Not applicable to live environments.
Optional dataExchangeApiUrl	The location of the data server. The default location is `http://${NL-ControllerIp}:7400/DataExchange/v1/Service.svc/`
Optional dataExchangeApiKey	The API key of the DataExchange API

Status codes

NL-DYNATRACE_MONITORING_ACTION-01: Could not parse arguments
NL-DYNATRACE_MONITORING_ACTION-02: Technical error
NL-DYNATRACE_MONITORING_ACTION-03: Bad context

Analyze results in NeoLoad

All the metrics retrieved from Dynatrace are available in the NeoLoad Controller under the External Data tab. The metrics are captured live during the test and also after the test has been executed. NeoLoad metrics

Analyze results in Dynatrace

Create a custom chart with the NeoLoad data.
Click the custom metric.
To analyze all the Neotys metrics, go to NeoLoad data.
Check the NeoLoad events on the tested application.

Limitations

The Dynatrace Neotys integration bundle doesn't work with NeoLoad Check User Path mode.