<?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 Re: Migration Python extension V1.0 to SQL Data source/extension 2.0 in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/263817#M5608</link>
    <description>&lt;P&gt;You'd have to ingest it as log lines instead of events. You can then extract events from said log lines in case you need it in that format.&lt;/P&gt;</description>
    <pubDate>Wed, 27 Nov 2024 11:46:51 GMT</pubDate>
    <dc:creator>Mike_L</dc:creator>
    <dc:date>2024-11-27T11:46:51Z</dc:date>
    <item>
      <title>Migration Python extension V1.0 to SQL Data source/extension 2.0</title>
      <link>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/263752#M5604</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I need some help/advice regarding migrating&amp;nbsp;Python extension V1.0 to SQL Data source extension 2.0 (&lt;A href="https://docs.dynatrace.com/docs/ingest-from/extensions20/data-sources/sql/sql-reference#monitoring-configuration" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/docs/ingest-from/extensions20/data-sources/sql/sql-reference&lt;/A&gt;) In python it executes some SQL queries which I can migrate to metrics or dimensions in SQL Data source extension 2.0. But at some point in extension V1.0 it uses python function&amp;nbsp;&lt;STRONG&gt;device.report_custom_info_event &lt;/STRONG&gt;which adds a info event to the custom device.&lt;/P&gt;
&lt;P&gt;How can migrate&amp;nbsp;&lt;STRONG&gt;report_custom_info_event to extension V2.0 &lt;/STRONG&gt;(SQL Data source)&lt;/P&gt;
&lt;P&gt;Thank you so much for your support&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 08:17:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/263752#M5604</guid>
      <dc:creator>detk72</dc:creator>
      <dc:date>2024-11-27T08:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: Migration Python extension V1.0 to SQL Data source/extension 2.0</title>
      <link>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/263817#M5608</link>
      <description>&lt;P&gt;You'd have to ingest it as log lines instead of events. You can then extract events from said log lines in case you need it in that format.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2024 11:46:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/263817#M5608</guid>
      <dc:creator>Mike_L</dc:creator>
      <dc:date>2024-11-27T11:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Migration Python extension V1.0 to SQL Data source/extension 2.0</title>
      <link>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/267418#M5828</link>
      <description>&lt;P&gt;Thanks I will try this&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 15:46:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Migration-Python-extension-V1-0-to-SQL-Data-source-extension-2-0/m-p/267418#M5828</guid>
      <dc:creator>detk72</dc:creator>
      <dc:date>2025-01-14T15:46:46Z</dc:date>
    </item>
  </channel>
</rss>

