<?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 PTA Plugins in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-plugins/m-p/1424713#M89801</link>
    <description>&lt;P&gt;Is there further information on what "No audit creator plugin was found for syslog" means from diamond.log or a log with further details? Does it mean parsing isn't successful?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Debugging is enabled for the plugin and ./TestCustomizedPlugin.sh shows the syslog matches and maps keys successfully, so I am not sure what the problem is &lt;/P&gt;</description>
    <pubDate>Thu, 14 May 2026 11:54:58 GMT</pubDate>
    <dc:creator>GGCC</dc:creator>
    <dc:date>2026-05-14T11:54:58Z</dc:date>
    <item>
      <title>PTA Plugins</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-plugins/m-p/1424713#M89801</link>
      <description>&lt;P&gt;Is there further information on what "No audit creator plugin was found for syslog" means from diamond.log or a log with further details? Does it mean parsing isn't successful?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Debugging is enabled for the plugin and ./TestCustomizedPlugin.sh shows the syslog matches and maps keys successfully, so I am not sure what the problem is &lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2026 11:54:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-plugins/m-p/1424713#M89801</guid>
      <dc:creator>GGCC</dc:creator>
      <dc:date>2026-05-14T11:54:58Z</dc:date>
    </item>
    <item>
      <title>Re: PTA Plugins</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-plugins/m-p/1424714#M89802</link>
      <description>&lt;P&gt;Understanding "No Audit Creator Plugin Was Found for Syslog"&lt;/P&gt;&lt;P&gt;Overview&lt;/P&gt;&lt;P&gt;The error message "No audit creator plugin was found for syslog" indicates an issue in the final stage of the log processing pipeline, not in parsing itself.&lt;/P&gt;&lt;P&gt;Pipeline Stages&lt;/P&gt;&lt;P&gt;1. Collection: Syslog message received&lt;/P&gt;&lt;P&gt; 2. Parsing: Fields extracted successfully&lt;/P&gt;&lt;P&gt; 3. Mapping: Keys normalized&lt;/P&gt;&lt;P&gt; 4. Audit Creation: Failure occurs here due to missing plugin&lt;/P&gt;&lt;P&gt;What This Means&lt;/P&gt;&lt;P&gt;The system cannot find a registered audit creator plugin to transform the parsed syslog data into a final event format.&lt;/P&gt;&lt;P&gt;Why Parsing Tests Pass&lt;/P&gt;&lt;P&gt;TestCustomizedPlugin.sh validates parsing and mapping only. It does not test runtime plugin registration or audit creation.&lt;/P&gt;&lt;P&gt;Common Root Causes&lt;/P&gt;&lt;P&gt;- Missing audit creator plugin&lt;/P&gt;&lt;P&gt; - Event type mismatch&lt;/P&gt;&lt;P&gt; - Missing required metadata&lt;/P&gt;&lt;P&gt; - Plugin not loaded at runtime&lt;/P&gt;&lt;P&gt; - Missing configuration mapping between parser and creator&lt;/P&gt;&lt;P&gt;Recommended Troubleshooting Steps&lt;/P&gt;&lt;P&gt;1. Verify audit creator plugins exist&lt;/P&gt;&lt;P&gt; 2. Check syslog mapping configuration&lt;/P&gt;&lt;P&gt; 3. Review full logs for plugin loading errors&lt;/P&gt;&lt;P&gt; 4. Inspect final event metadata&lt;/P&gt;&lt;P&gt; 5. Test with a known working event type&lt;/P&gt;&lt;P&gt;Key Takeaway&lt;/P&gt;&lt;P&gt;Parsing is successful. The issue lies in audit creator plugin resolution or configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2026 11:17:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-plugins/m-p/1424714#M89802</guid>
      <dc:creator>RobertS_Cyberark</dc:creator>
      <dc:date>2026-06-15T11:17:21Z</dc:date>
    </item>
  </channel>
</rss>

