<?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 XSIAM Parsing Success Rate Metrics in Cortex XSIAM Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-parsing-success-rate-metrics/m-p/1244684#M293</link>
    <description>&lt;P&gt;Hi Team,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to calculate&amp;nbsp;Parsing Success Rate Metrics&amp;nbsp; in XSIAM i.e.,&amp;nbsp;% of events successfully parsed into SIEM schema.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Wincy&lt;/P&gt;</description>
    <pubDate>Fri, 26 Dec 2025 09:58:31 GMT</pubDate>
    <dc:creator>W.Kishore594287</dc:creator>
    <dc:date>2025-12-26T09:58:31Z</dc:date>
    <item>
      <title>XSIAM Parsing Success Rate Metrics</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-parsing-success-rate-metrics/m-p/1244684#M293</link>
      <description>&lt;P&gt;Hi Team,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to calculate&amp;nbsp;Parsing Success Rate Metrics&amp;nbsp; in XSIAM i.e.,&amp;nbsp;% of events successfully parsed into SIEM schema.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Wincy&lt;/P&gt;</description>
      <pubDate>Fri, 26 Dec 2025 09:58:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-parsing-success-rate-metrics/m-p/1244684#M293</guid>
      <dc:creator>W.Kishore594287</dc:creator>
      <dc:date>2025-12-26T09:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: XSIAM Parsing Success Rate Metrics</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-parsing-success-rate-metrics/m-p/1247938#M335</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/989691125"&gt;@W.Kishore594287&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Greetings for the day.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, it is possible to calculate Parsing Success Rate metrics in Cortex XSIAM using XQL queries. While XSIAM does not provide a single out-of-the-box "Parsing Success Rate" metric, you can derive this percentage by querying internal datasets that track ingestion errors and comparing them against total ingestion volumes.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;Recommended Methods for Calculation:&lt;/H4&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;1. Utilizing the &lt;CODE&gt;parsing_rules_errors&lt;/CODE&gt; Dataset&lt;/H4&gt;
&lt;P&gt;Cortex XSIAM tracks explicit parsing failures in the &lt;CODE&gt;parsing_rules_errors&lt;/CODE&gt; dataset. This table records "Data Format" errors and specific failures encountered when a parsing rule fails to process a log entry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To calculate the rate, you can compare the count of errors in this table against the total event count from the &lt;CODE&gt;metrics_source&lt;/CODE&gt; dataset or the relevant target log dataset.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;2. Analyzing Null Values in Mapped Fields (Log Drift Detection)&lt;/H4&gt;
&lt;P&gt;For many integrations, if a log fails to parse correctly, the XSIAM ingestion engine may still ingest the record but place the entire content into the &lt;CODE&gt;_raw_log&lt;/CODE&gt; field while leaving schema-defined fields (such as &lt;CODE&gt;action&lt;/CODE&gt;, &lt;CODE&gt;src_ip&lt;/CODE&gt;, etc.) as &lt;CODE&gt;NULL&lt;/CODE&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A common best practice for monitoring parsing success and detecting log drift is to generate a report on the percentage of &lt;CODE&gt;NULL&lt;/CODE&gt; values in key mandatory fields over a specific period. If the log format changes at the source and the parser is no longer compatible, the percentage of &lt;CODE&gt;NULL&lt;/CODE&gt; values will typically increase significantly.&lt;/P&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;Example XQL Logic:&lt;/H4&gt;
&lt;P&gt;To calculate the success rate for a specific dataset, you can use logic similar to the following (based on the null-check methodology commonly used for monitoring log drift):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class="language-sql"&gt;dataset = &amp;lt;your_dataset_name_raw&amp;gt;
| comp 
    count(_id) as total_events, 
    count(xdm.event.type) as parsed_events   // Replace with a key field that should always be parsed
| alter success_rate = (parsed_events * 100.0 / total_events)
| fields total_events, parsed_events, success_rate
&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&lt;STRONG&gt;In this logic:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;total_events&lt;/CODE&gt; represents all ingested logs.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;parsed_events&lt;/CODE&gt; represents logs where a mandatory parsed field is populated.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;CODE&gt;success_rate&lt;/CODE&gt; gives the parsing success percentage.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;H4&gt;&amp;nbsp;&lt;/H4&gt;
&lt;H4&gt;Monitoring Tools in XSIAM&lt;/H4&gt;
&lt;P&gt;&lt;STRONG&gt;Command Center Dashboard:&lt;/STRONG&gt; Provides high-level interactive overviews of system activity and overall ingestion rates, though it may not display granular parsing success percentages by default.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;CODE&gt;metrics_view&lt;/CODE&gt; Preset:&lt;/STRONG&gt; Can be used to monitor daily data ingestion rates and identify periods of unusually low ingestion, which may indicate parsing or collection issues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Health Alerts:&lt;/STRONG&gt; XSIAM generates health alerts for "Data Format" errors or when logs are not collected for an abnormally long period.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For complex environments where logs are ingested through multiple custom parsers, you can aggregate errors from the &lt;CODE&gt;parsing_rules_errors&lt;/CODE&gt; dataset by vendor and product to identify specific integrations with lower parsing success rates.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you feel this has answered your query, please let us know by clicking like and on&amp;nbsp;&lt;STRONG&gt;"mark this as a Solution".&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;S. Subashkar Sekar&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 14:06:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsiam-discussions/xsiam-parsing-success-rate-metrics/m-p/1247938#M335</guid>
      <dc:creator>susekar</dc:creator>
      <dc:date>2026-02-11T14:06:06Z</dc:date>
    </item>
  </channel>
</rss>

