<?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: User Session Export to ElasticSearch has a different schema to the &amp;quot;click here to download sample&amp;quot; option in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58205#M190</link>
    <description>&lt;P&gt;We reworked the schema to be easier to parse/handle and to streamline used terms. There is an option "use new export format" which allows to toggle between the two formats in case you still have processing based on the old format. The new format is already the default for new customers and support for the previous format will be removed at some point. &lt;/P&gt;&lt;P&gt;Depending on this toggle, you should get the corresponding format in both places, i.e. the "click here to download sample" and the actually exported documents.&lt;/P&gt;</description>
    <pubDate>Thu, 08 Mar 2018 07:52:03 GMT</pubDate>
    <dc:creator>dominik_stadler</dc:creator>
    <dc:date>2018-03-08T07:52:03Z</dc:date>
    <item>
      <title>User Session Export to ElasticSearch has a different schema to the "click here to download sample" option</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58204#M189</link>
      <description>&lt;P&gt;What's the difference between the two exports? (Click to download from the User Session Export page and the json structure in ElasticSearch).&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Rupert&lt;/P&gt;</description>
      <pubDate>Tue, 27 Apr 2021 15:30:26 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58204#M189</guid>
      <dc:creator>rogilvie</dc:creator>
      <dc:date>2021-04-27T15:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: User Session Export to ElasticSearch has a different schema to the "click here to download sample" option</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58205#M190</link>
      <description>&lt;P&gt;We reworked the schema to be easier to parse/handle and to streamline used terms. There is an option "use new export format" which allows to toggle between the two formats in case you still have processing based on the old format. The new format is already the default for new customers and support for the previous format will be removed at some point. &lt;/P&gt;&lt;P&gt;Depending on this toggle, you should get the corresponding format in both places, i.e. the "click here to download sample" and the actually exported documents.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 07:52:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58205#M190</guid>
      <dc:creator>dominik_stadler</dc:creator>
      <dc:date>2018-03-08T07:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: User Session Export to ElasticSearch has a different schema to the "click here to download sample" option</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58206#M191</link>
      <description>&lt;P&gt;Thanks Dominik - I think we exported using the link in the old format, then turned on the export to elasticsearch using the new format. &lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Rupert&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 11:34:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58206#M191</guid>
      <dc:creator>rogilvie</dc:creator>
      <dc:date>2018-03-08T11:34:27Z</dc:date>
    </item>
    <item>
      <title>Re: User Session Export to ElasticSearch has a different schema to the "click here to download sample" option</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58207#M192</link>
      <description>&lt;P&gt;Oh is it possible to get a copy of the schema please? We're having a few issues with things like the max varchar size when exporting/importing the data to a DB. &lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rupert&lt;/P&gt;</description>
      <pubDate>Thu, 08 Mar 2018 11:37:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58207#M192</guid>
      <dc:creator>rogilvie</dc:creator>
      <dc:date>2018-03-08T11:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: User Session Export to ElasticSearch has a different schema to the "click here to download sample" option</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58208#M193</link>
      <description>&lt;P&gt;Hello;&lt;/P&gt;&lt;P&gt;The amount of crashes from Dynatrace to ELK are not traveling.&lt;/P&gt;&lt;P&gt;In the new format we have an arrays "errors" but only travel 1 record I have to map correctly?&lt;/P&gt;&lt;P&gt;or will it not be possible to have these data in ELK?&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;P&gt;-RobertoGuerrero&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Oct 2018 01:41:56 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/User-Session-Export-to-ElasticSearch-has-a-different-schema-to/m-p/58208#M193</guid>
      <dc:creator>rguerrero</dc:creator>
      <dc:date>2018-10-30T01:41:56Z</dc:date>
    </item>
  </channel>
</rss>

