Getting Data In

Where and how do I configure a sourcetype for generic xml?

dorbi
Explorer

Hey there!

I'm trying to monitor(batch)) a folder congaing  xml files, 

the XML files don't necessarily have the same structure, also they have multiple hierarchy and the level of it might vary .

where and how do i configure a sourcetype the know's how to handle this kind of a case so i won't have to parse the data with rex on search time.

 

example for a file that may exists:

dorbi_0-1671549060796.png

 

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The rex command is very flexible, but there are others you can use.  Consider xpath and xmlkv.

In props.conf, consider using KV_MODE = xml to have Splunk automatically extract fields.

---
If this reply helps you, Karma would be appreciated.

dorbi
Explorer

Writing regex with Rex field =_raw.. 

Is a great solution but I would like to do it at source type level so I won't have to write long and complicated querys.

I tried xmlkv and kv_mode = xml both doesn't extract fields with 2 or more levels of hierarchy so I'm missing a lot of fields.

Any more suggestions please?

 

 

 

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Have you tried KV_MODE = xml in props.conf?

---
If this reply helps you, Karma would be appreciated.
0 Karma

dorbi
Explorer

is there a way to see how it will work before applying it ? 

so if it won't work as planned i won't have to delete all the data inserted?

did you happen to check how it works on generic xml files or any sample from some place else?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Regrettably, there is no way to see how fields will be extracted before ingesting data.  The Extract FIeld wizard lets you preview extractions, but requires onboarded events.

This is a good use for a test system, even if it's your workstation.  Capture some sample data in a file, transfer the file to the test system and experiment with field extractions there.  Once you have it working as desired, export the settings in an app for installation in Production.  When you're done, just delete the index you used for testing.

If you can't use a test system then you'll have to test in Production.  Use a separate index (I call mine "test") until you have the extractions working right.  Since you're likely to be using search-time extractions, you should need to ingest the data only once.

---
If this reply helps you, Karma would be appreciated.
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 Certification at ...

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 ...