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
Get Updates on the Splunk Community!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...