Splunk Search

servicenow incidents in splunk

surekhasplunk
Communicator

AM not able to see all the incidents which are there in my servicenow instance.
I have splunk_TA_Snow app configured in my splunk.
and am getting below error in splnk_ta_snow_main log file.

2016-10-16 15:49:34,318 INFO pid=9600 tid=Thread-2 file=snow_data_loader.py:do_collect:153 | start https://accenturenordicspov.service-now.com/api/now/table/incident?sysparm_display_value=all&sysparm...
2016-10-16 15:49:35,229 INFO pid=9600 tid=Thread-2 file=snow_data_loader.py:_do_collect:170 | end https://accenturenordicspov.service-now.com/api/now/table/incident?sysparm_display_value=all&sysparm...
2016-10-16 15:49:35,234 INFO pid=9600 tid=Thread-2 file=snow_data_loader.py:collect_data:143 | Get 0 records from https://accenturenordicspov.service-now.com/incident
2016-10-16 15:49:35,236 INFO pid=9600 tid=Thread-2 file=snow_job_factory.py:
call_:50 | End collecting from incident.

0 Karma

ThomasLeroy
Explorer

Hello surekhasplunk,

There are no errors in your log file.

The TA_snow just can't find any new records created after sys_updated_on>=2016-10-07.

Check your input.conf, you can add this option :

since_when = your_date

The TA_snow will start collecting from your_date until today.
Next by default he will check every two minutes if they are updates on your table.

Hope this help

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...