﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>LogViewPlus Support » LogViewPlus Support » Help &amp; Support  » Same file extension but different format</title><generator>InstantForum 2017-1 Final</generator><description>LogViewPlus Support</description><link>https://www.logviewplus.com/forum/</link><webMaster>LogViewPlus Support</webMaster><lastBuildDate>Mon, 13 Apr 2026 11:47:27 GMT</lastBuildDate><ttl>20</ttl><item><title>Same file extension but different format</title><link>https://www.logviewplus.com/forum/post/2040</link><description>We have log files with different formats (CSV and XML) but with the same file extension. I hoped that the parser mappings will be processed top down switching to the next parser (for the current file extension) if the current one could not parse the file. But it seems like this is not done.&lt;br/&gt;&lt;br/&gt;Is there any way to deal with that?</description><pubDate>Thu, 01 Feb 2024 07:06:37 GMT</pubDate><dc:creator>May</dc:creator></item><item><title>RE: Same file extension but different format</title><link>https://www.logviewplus.com/forum/post/2051</link><description>Perfect! Just what I was looking for. Th</description><pubDate>Thu, 01 Feb 2024 07:06:37 GMT</pubDate><dc:creator>May</dc:creator></item><item><title>RE: Same file extension but different format</title><link>https://www.logviewplus.com/forum/post/2047</link><description>The default parser lookup behaviour is to apply the first matching parser configuration, but this can be changed by using the &lt;a href="https://www.logviewplus.com/docs/parser_mappings.html" id="if_insertedNode_1706701145005"&gt;Heuristic Strategy&lt;/a&gt; instead.&amp;nbsp; The heuristic strategy will use multiple parsers to parse a log file and then apply the best one.&lt;br/&gt;&lt;br/&gt;Hope that helps,&lt;br/&gt;&lt;br/&gt;Toby</description><pubDate>Wed, 31 Jan 2024 11:40:30 GMT</pubDate><dc:creator>LogViewPlus Support</dc:creator></item></channel></rss>