Splunk Search

Field failing to extract (ServiceNow)

shazbot79
Path Finder

Hi,

I have used the Service Now add on to pull in the incident table. We have a custom SNow field called "dv_u_configuration_item__generic_" which hasn't extracted and also isn't searchable. Is there something about this field name that could cause issues?

Labels (2)
0 Karma
1 Solution

shazbot79
Path Finder

Hi, thanks for this. I have other custom fields from Service Now that have extracted fine though so I'm not sure it is the custom nature that is the issue... I have extracted the field using regex as a work around. I just would like to understand what the issue is. Thanks

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Is it's a custom field then the TA doesn't know to extract it.  Consider modifying the TA (in local) to support your field.

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

shazbot79
Path Finder

Hi, thanks for this. I have other custom fields from Service Now that have extracted fine though so I'm not sure it is the custom nature that is the issue... I have extracted the field using regex as a work around. I just would like to understand what the issue is. Thanks

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

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

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...

Index This | How many sevens are there between 1 and 100?

August 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...