Dashboards & Visualizations

PARSER: Applying Intentions failed 'unicode' object has no attribute 'get'

blurblebot
Communicator

Though this has been discussed on Splunk Answers, the prevailing solution has not worked for me.

As per the discussions on Splunk Answers, I've switched the "intention" and "replacementMap" params in my xml, but as soon as I populate the search field, the error is thrown. If I leave it blank, it uses the default value from the xml, but that's as much luck as I can wrangle.

Below is the EFS section modified as per prevailing recommendations:

<module name="ExtendedFieldSearch"
layoutPanel="viewHeader">
     <param name="intention">
     <param name="name">stringreplace</param>
     <param name="arg">
    <param name="sourcetypeToken">
       <param name="default">*</param>
       <param name="fillOnEmpty">True</param>
     </param>
   </param>
 </param>   <param name="replacementMap">
   <param name="arg">
     <param name="sourcetypeToken"/>
   </param>
 </param>
 <param name="field">sourcetype</param>
 <param name="q">splunkd</param> 

...

Tags (1)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

You are right that the "accepted" answer here is wrong. However, the other upvoted answer by dmlee is correct.

Swapping the sections I would not expect to have any effect. However, your replacmentMap arg needs a value:

<module name="ExtendedFieldSearch" layoutPanel="viewHeader">
  <param name="intention">
    <param name="name">stringreplace</param>
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="default">*</param>
        <param name="fillOnEmpty">True</param>
      </param>
    </param>
  </param>   
  <param name="replacementMap">
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="value"></param>
      </param>
    </param>
  </param>
  <param name="field">sourcetype</param>
  <param name="q">splunkd</param> 

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

You are right that the "accepted" answer here is wrong. However, the other upvoted answer by dmlee is correct.

Swapping the sections I would not expect to have any effect. However, your replacmentMap arg needs a value:

<module name="ExtendedFieldSearch" layoutPanel="viewHeader">
  <param name="intention">
    <param name="name">stringreplace</param>
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="default">*</param>
        <param name="fillOnEmpty">True</param>
      </param>
    </param>
  </param>   
  <param name="replacementMap">
    <param name="arg">
      <param name="sourcetypeToken">
        <param name="value"></param>
      </param>
    </param>
  </param>
  <param name="field">sourcetype</param>
  <param name="q">splunkd</param> 

r999
Path Finder

what have you changed? only added

?

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...