<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Specifications of Live Debugger in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Specifications-of-Live-Debugger/m-p/278847#M36694</link>
    <description>&lt;P&gt;Could you please explain the specifications of Live Debugger?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The UI of LiveDebugger displays the source code, but typically, source code is not deployed to production servers—instead, compiled binaries are deployed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Am I correct in understanding that there is no need to deploy source code in the production environment, and that the tool is used in conjunction with development tools (such as the VS Code extension or JetBrains plugin), connected to a version control system like Git, with access to the released version of the code?&lt;/P&gt;
&lt;P&gt;BestRegards,&lt;BR /&gt;Kohei Otsuka&lt;/P&gt;</description>
    <pubDate>Mon, 09 Jun 2025 07:59:34 GMT</pubDate>
    <dc:creator>kohtsuka</dc:creator>
    <dc:date>2025-06-09T07:59:34Z</dc:date>
    <item>
      <title>Specifications of Live Debugger</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Specifications-of-Live-Debugger/m-p/278847#M36694</link>
      <description>&lt;P&gt;Could you please explain the specifications of Live Debugger?&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The UI of LiveDebugger displays the source code, but typically, source code is not deployed to production servers—instead, compiled binaries are deployed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Am I correct in understanding that there is no need to deploy source code in the production environment, and that the tool is used in conjunction with development tools (such as the VS Code extension or JetBrains plugin), connected to a version control system like Git, with access to the released version of the code?&lt;/P&gt;
&lt;P&gt;BestRegards,&lt;BR /&gt;Kohei Otsuka&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jun 2025 07:59:34 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Specifications-of-Live-Debugger/m-p/278847#M36694</guid>
      <dc:creator>kohtsuka</dc:creator>
      <dc:date>2025-06-09T07:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: Specifications of LiveDebugger</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Specifications-of-Live-Debugger/m-p/278853#M36695</link>
      <description>&lt;P&gt;You don't need to upload your source code anywhere. Dynatrace does not have access to your source code. Live debugger is used in conjunction with your IDE (Jetbrains / VSCode have plugins) or you can use the live debugger app in Dynatrace UI to setup breakpoints and view snapshots. If you are using the Live debugger app and the source code is local (not on GitHub or other supported services), you just need to download the Dynatrace Desktop App (not the best name chosen for its functionality), which acts as a sidecar on your desktop. Live debugger app in Dynatrace UI then accesses the source code using this sidecar. Everything lives in your browser. The source code does not get uploaded.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jun 2025 07:50:52 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Specifications-of-Live-Debugger/m-p/278853#M36695</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2025-06-06T07:50:52Z</dc:date>
    </item>
  </channel>
</rss>

