<?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>question Re: Ingesting XML Telemetry in Metron in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ingesting-XML-Telemetry-in-Metron/m-p/147443#M56635</link>
    <description>&lt;P&gt;Metron supports 3 types of parsers: Grok, CSV and Java.   For XML data Java is the best choice.  &lt;/P&gt;&lt;P&gt;You can see example parsers in the Metron github:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers"&gt;https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You could also use Nifi to convert the XML to JSON and enqueue the events to the enrichment topic.   Here are some articles about parsing XML logs with Nifi:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/25720/parsing-xml-logs-with-nifi-part-1-of-3.html"&gt;https://community.hortonworks.com/articles/25720/parsing-xml-logs-with-nifi-part-1-of-3.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 31 Mar 2017 19:59:58 GMT</pubDate>
    <dc:creator>Carolyn</dc:creator>
    <dc:date>2017-03-31T19:59:58Z</dc:date>
    <item>
      <title>Ingesting XML Telemetry in Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ingesting-XML-Telemetry-in-Metron/m-p/147442#M56634</link>
      <description>&lt;P&gt;
	Hi,&lt;/P&gt;&lt;P&gt;
	I was wondering about the best way to ingest logs in XML format into Metron. Parsing with Grok doesn't seem to be the way to go in this case. Remaining options seem to be to 1) either utilize NiFi to turn the XML into a format that Metron expects, 2) or develop a java parser for parsing XML, (that is Metron-288 issue which is not of high priority: &lt;A href="https://issues.apache.org/jira/browse/METRON-288" target="_blank"&gt;https://issues.apache.org/jira/browse/METRON-288&lt;/A&gt; ). &lt;/P&gt;&lt;P&gt;Are these two options the only possibilities? &lt;/P&gt;</description>
      <pubDate>Thu, 09 Mar 2017 07:45:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ingesting-XML-Telemetry-in-Metron/m-p/147442#M56634</guid>
      <dc:creator>hamed1</dc:creator>
      <dc:date>2017-03-09T07:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: Ingesting XML Telemetry in Metron</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ingesting-XML-Telemetry-in-Metron/m-p/147443#M56635</link>
      <description>&lt;P&gt;Metron supports 3 types of parsers: Grok, CSV and Java.   For XML data Java is the best choice.  &lt;/P&gt;&lt;P&gt;You can see example parsers in the Metron github:&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers"&gt;https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You could also use Nifi to convert the XML to JSON and enqueue the events to the enrichment topic.   Here are some articles about parsing XML logs with Nifi:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/articles/25720/parsing-xml-logs-with-nifi-part-1-of-3.html"&gt;https://community.hortonworks.com/articles/25720/parsing-xml-logs-with-nifi-part-1-of-3.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 19:59:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ingesting-XML-Telemetry-in-Metron/m-p/147443#M56635</guid>
      <dc:creator>Carolyn</dc:creator>
      <dc:date>2017-03-31T19:59:58Z</dc:date>
    </item>
  </channel>
</rss>

