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!

Built-in Service Level Objectives Management to Bridge the Gap Between Service & ...

Wednesday, May 29, 2024  |  11AM PST / 2PM ESTRegister now and join us to learn more about how you can ...

Get Your Exclusive Splunk Certified Cybersecurity Defense Engineer at Splunk .conf24 ...

We’re excited to announce a new Splunk certification exam being released at .conf24! If you’re headed to Vegas ...

Share Your Ideas & Meet the Lantern team at .Conf! Plus All of This Month’s New ...

Splunk Lantern is Splunk’s customer success center that provides advice from Splunk experts on valuable data ...