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!

Splunk Enterprise Security 8.0.2 Availability: On cloud and On-premise!

A few months ago, we released Splunk Enterprise Security 8.0 for our cloud customers. Today, we are excited to ...

Logs to Metrics

Logs and Metrics Logs are generally unstructured text or structured events emitted by applications and written ...

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...