Splunk Search

Extract xml

vasanthmss
Motivator

Hi Splunkers,

I would like to extract the following xml while indexing..

fields:

host=0.0.0.1
source=mysource
sourcetype=mysourcetype
name=vasu
address=us

xml:

<customvalues>
    <customvalue>
        <name>host</name>
        <value>0.0.0.1</value>      
    </customvalue>
    <customvalue>
        <name>source</name>
        <value>mysource</value>     
    </customvalue>
    <customvalue>
        <name>sourcetype</name>
        <value>mysourcetype</value>     
    </customvalue>
    <customvalue>
        <name>name</name>
        <value>vasu</value>     
    </customvalue>
    <customvalue>
        <name>address</name>
        <value>US</value>       
    </customvalue>
</customvalues>
V
Tags (1)
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

You could set this in props.conf for that sourcetype:

SEDCMD-foo = s/(?s).*?<name>([^<]+).*?<value>([^<]+)(\s*<\/[^>]+>)*/\1="\2" /g

That'll turn your event into this at index time:

host="0.0.0.1" source="mysource" sourcetype="mysourcetype" name="vasu" address="US" 

Note, this will not set Splunk's metadata fields host, source, sourcetype automatically - that requires a bit more rewriting in transforms.conf if that's what you're after.

Note, your closing tags aren't valid XML... also, this kind of data structure sucks to work with.

View solution in original post

splunker12er
Motivator
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

You could set this in props.conf for that sourcetype:

SEDCMD-foo = s/(?s).*?<name>([^<]+).*?<value>([^<]+)(\s*<\/[^>]+>)*/\1="\2" /g

That'll turn your event into this at index time:

host="0.0.0.1" source="mysource" sourcetype="mysourcetype" name="vasu" address="US" 

Note, this will not set Splunk's metadata fields host, source, sourcetype automatically - that requires a bit more rewriting in transforms.conf if that's what you're after.

Note, your closing tags aren't valid XML... also, this kind of data structure sucks to work with.

vasanthmss
Motivator

Thanks Martin_Muller,

actually its my mistake, now changed the question with proper tags,I will give a try and update it.

V
0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...