Deployed d7248be with MkDocs version: 1.6.0

getting-started/index.html

@@ -627,7 +627,7 @@ <h3 id="create-api-token">Create API Token<a class="headerlink" href="#create-ap
 </ul>
 <h4 id="api-token-permissions-explained">API Token Permissions Explained<a class="headerlink" href="#api-token-permissions-explained" title="Permanent link">#</a></h4>
 <ul>
-<li><code>logs.ingest</code>, <code>metrics.ingest</code>, and <code>openTelemetryTrace.ingest</code> are required to send OpenTelemetry data into Dynatrace</li>
+<li><code>logs.ingest</code> is required to send log entries into Dynatrace</li>
 <li><code>events.ingest</code> is required to send the <code>CUSTOM_CONFIGURATION</code> event into Dynatrace</li>
 </ul>
 <h2 id="start-demo">Start Demo<a class="headerlink" href="#start-demo" title="Permanent link">#</a></h2>

introduce-change/index.html

@@ -574,30 +574,23 @@ <h1>6. Introduce System Change</h1>
 <p>This simulates releasing new functionality to your users in production.</p>
 <h2 id="inform-dynatrace">Inform Dynatrace<a class="headerlink" href="#inform-dynatrace" title="Permanent link">#</a></h2>
 <p>First, inform Dynatrace that a change is about to occur.
-Namely, you are going to change the <code>cartServiceFailure</code> feature flag from <code>off</code> to <code>on</code>.</p>
+Namely, you are going to make a change to the <code>my-otel-demo-cartservice</code> service 
+by changing the <code>cartServiceFailure</code> feature flag from <code>off</code> to <code>on</code>.</p>
 <p>Tell Dynatrace about the upcoming change by sending an event (note: This event does <strong>not</strong> actually make the change; you need to do this).</p>
-<p>A wrapper script to help you with this.</p>
 <p>Run the following:</p>
-<div class="highlight"><pre><span></span><code>./runtimeChange.sh cartservice cartServiceFailure on
+<div class="highlight"><pre><span></span><code>./runtimeChange.sh my-otel-demo-cartservice cartServiceFailure on
 </code></pre></div>
-<p>You should see output signifying an event has been successfully sent:</p>
-<div class="highlight"><pre><span></span><code>{
-  &quot;reportCount&quot;:1,
-  &quot;eventIngestResults&quot;:[{
-    &quot;correlationId&quot;:&quot;abcd1234abcd1234&quot;,
-    &quot;status&quot;:&quot;OK&quot;
-  }]
-}
-</code></pre></div>
-<p>Refresh the <code>cartservice</code> page and near the bottom you should see the configuration change event.</p>
+<p>Refresh the <code>my-otel-demo-cartservice</code> page and near the bottom you should see the configuration change event.</p>
 <p><img alt="configuration changed event" src="../images/configuration-change-event.png" /></p>
 <h2 id="make-change">Make Change<a class="headerlink" href="#make-change" title="Permanent link">#</a></h2>
-<p>Open this file: <code>.devcontainer/otel-demo/flags.yaml</code></p>
+<p>Open this file: <code>flags.yaml</code></p>
 <p>Change the <code>defaultValue</code> of <code>cartServiceFailure</code> from <code>"off"</code> to <code>"on"</code> (line Scroll to line <code>75</code>)</p>
 <p><img alt="feature flag YAML" src="../images/change-feature-flag.png" /></p>
 <p>Now apply the change by running this command:</p>
-<div class="highlight"><pre><span></span><code>kubectl apply -f .devcontainer/otel-demo/flags.yaml
+<div class="highlight"><pre><span></span><code>kubectl apply -f $CODESPACE_VSCODE_FOLDER/flags.yaml
 </code></pre></div>
+<p>The application will now generate errors when emptying the users cart.
+It will do this 1/10th of the time, so be patient, it can take a few moments for the errors to occur.</p>
 <div class="grid cards">
 <ul>
 <li><a href="../review-problem/">Click Here to Continue <span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span></a></li>

review-problem/index.html

@@ -598,7 +598,7 @@ <h1>7. Review Problem</h1>
 <p><img alt="problem screen" src="../images/problem-screen.png" /></p>
 <h2 id="explore-problem-details">Explore Problem Details<a class="headerlink" href="#explore-problem-details" title="Permanent link">#</a></h2>
 <p><img alt="problem details" src="../images/problem-details.png" /></p>
-<p>Opening the problem record, you will see that it has effected one entity: the <code>cartservice</code>.</p>
+<p>Opening the problem record, you will see that it has effected one entity: the <code>my-otel-demo-cartservice</code>.</p>
 <p>Navigate to the <code>Logs</code> panel. Click <code>Run query</code> next to <code>Show x errors</code> (your number of errors may differ from the screenshot)</p>
 <p><img alt="logs panel 1" src="../images/logs-panel-1.png" /></p>
 <p>Expand the log entry and notice you have some key metadata available:</p>
@@ -668,7 +668,7 @@ <h2 id="reveal-the-root-cause">Reveal the root cause<a class="headerlink" href="
 </div>
 <div class="grid cards">
 <ul>
-<li><a href="../cleanup/">Click Here to Continue <span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span></a></li>
+<li><a href="../cleanup/">Click Here to Begin <span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span></a></li>
 </ul>
 </div>
 

view-observability-data/index.html

@@ -493,13 +493,15 @@
 
   <h1>5. Validate Observability Data</h1>
 
-<p><img alt="services screen" src="../images/services-screen.png" /></p>
 <p>In Dynatrace, press <code>ctrl + k</code> and search for <code>Services</code>. Dynatrace creates service entities based on the incoming span data.
 The logs are also available for each service.</p>
 <p>You can also query data via <a href="https://docs.dynatrace.com/docs/observe-and-explore/dashboards-and-notebooks/notebooks" target="_blank">notebooks</a>
 and <a href="https://docs.dynatrace.com/docs/observe-and-explore/dashboards-and-notebooks/dashboards-new" target="_blank">dashboards</a> (<code>ctrl + k</code> and search for <code>notebooks</code> or <code>dashboards</code>).</p>
-<p>During this tutorial we will be working with the <code>cartservice</code>.</p>
-<p><img alt="cartservice screen" src="../images/cartservice-screen.png" /></p>
+<p>For example, to validate logs are available for <code>cartservice</code>:</p>
+<div class="highlight"><pre><span></span><code>fetch logs
+| filter service.name == &quot;cartservice&quot;
+| limit 10
+</code></pre></div>
 <div class="grid cards">
 <ul>
 <li><a href="../introduce-change/">Click Here to Continue <span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span></a></li>