Skip to content

Commit

Permalink
Deployed d21f586 with MkDocs version: 1.6.0
Browse files Browse the repository at this point in the history
  • Loading branch information
agardnerIT committed Sep 18, 2024
1 parent f7aba0d commit e2bbda0
Show file tree
Hide file tree
Showing 4 changed files with 54 additions and 1 deletion.
Binary file added images/load-test-integration-flow.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
53 changes: 53 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -317,6 +317,15 @@
</span>
</a>

</li>

<li class="md-nav__item">
<a href="#logical-architecture" class="md-nav__link">
<span class="md-ellipsis">
Logical Architecture
</span>
</a>

</li>

<li class="md-nav__item">
Expand Down Expand Up @@ -589,6 +598,15 @@
</span>
</a>

</li>

<li class="md-nav__item">
<a href="#logical-architecture" class="md-nav__link">
<span class="md-ellipsis">
Logical Architecture
</span>
</a>

</li>

<li class="md-nav__item">
Expand Down Expand Up @@ -641,6 +659,41 @@ <h2 id="a-new-release">A New Release<a class="headerlink" href="#a-new-release"
<li>Make the "go / no go" decision for that feature.</li>
<li>Provide feedback on why you made the decision you did.</li>
</ul>
<h2 id="logical-architecture">Logical Architecture<a class="headerlink" href="#logical-architecture" title="Permanent link">#</a></h2>
<p>Below is the "flow" of information and actors during this demo.</p>
<p>This architecture also holds true for other load testing tools (eg. JMeter).</p>
<ol>
<li>
<p>A load test is executed.
The HTTP requests are annotated with <a href="https://docs.dynatrace.com/docs/platform-modules/automations/cloud-automation/test-automation#tag-tests-with-http-headers" target="_blank">the standard header values</a>.</p>
</li>
<li>
<p>Metrics are streamed during the load test (if the load testing tool supports this)
or the metrics are send at the end of the load test.</p>
</li>
<li>
<p>The load testing tool is responsible for sending an SDLC event to signal "test is finished".
Integrators are responsible for crafting this event to contain any important information required by Dynatrace
such as the test duration.</p>
</li>
<li>
<p>A <a href="https://docs.dynatrace.com/docs/platform-modules/automations/workflows" target="_blank">workflow</a> is triggered on receipt of this event.
The workflow triggers the <a href="https://docs.dynatrace.com/docs/platform-modules/automations/site-reliability-guardian" target="_blank">Site Reliability Guardian</a>.</p>
</li>
<li>
<p>The Site Reliability Guardian processes the load testing metrics and to provide an automated load testing report.
This can be used for information only or can be used as an automated "go / no go" decision point.</p>
</li>
<li>
<p>Dynatrace users can view the results in a dashboard, notebook or use the result as a trigger for further automated workflows.</p>
</li>
<li>
<p>Integrators have the choice to send (emit) the results to an external tool.
This external tool can then use this result.
One example would be sending the SRG result to Jenkins to progress or prevent a deployment.</p>
</li>
</ol>
<p><img alt="Logical Architecture" src="images/load-test-integration-flow.jpg" /></p>
<h2 id="compatibility">Compatibility<a class="headerlink" href="#compatibility" title="Permanent link">#</a></h2>
<table>
<thead>
Expand Down
Loading

0 comments on commit e2bbda0

Please sign in to comment.