Tutorial Feedback

Use the form below to provide feedback on this page / tutorial as a whole.

Skip to content

3. Run Demo

No Traffic?#

Expect No Traffic in Dynatrace

You won't see these values (or any traffic in Dynatrace) by default because the load test is hitting example.com

If you have a service instrumented with OneAgent or OpenTelemetry, modify example.jmx to hit your URL instead to see traffic.

Tear Down Thread Group#

A tearDown thread group exists (which fires at the end of the load test)

  • This request is a POST to /platform/ingest/v1/events.sdlc with a JSON payload
  • The request has header values set for Content-Type and Authorization

This event allows integration opportunitities into other Dynatrace functionality such as triggering workflows automatically at the end of a load test.

Run JMeter#

Paste the following into the terminal to run a 10 second load test and automatically send the SDLC event to Dynatrace:

/workspaces/$RepositoryName/apache-jmeter/bin/jmeter.sh -n -t /workspaces/$RepositoryName/jmeterscripts/example.jmx

View Events#

When the load test finished, the teardown thread group sends a Software Delivery Lifecycle Event (SDLC) to Dynatrace.

teardown call

Notice that the event contains metadata such as the provider and service which can be used for filtering in Dynatrace (see DQL below).

This event can be used as a trigger Dynatrace for workflows, synthetic tests, the site reliability guardian and more.

In Dynatrace:

  • Press ctrl + k and search for notebooks
  • Open an existing notebook or create a new one
  • Add a new DQL section and paste the following
fetch events
| filter event.kind == "SDLC_EVENT"
| filter event.provider == "jmeter"
| filter event.category == "finished"

sdlc event

The demo is complete.