What is the easiest way to debug inbound REST?

[John VanBruggen]

I am trying to troubleshoot a WebServices import table.
We are using REST to send the data to the table.

The table is configured as a WebServices import table so it automatically transforms the data as it is being loaded.

Various URLs have been tested with the same results.

https://{INSTANCENAME}.service-now.com/{TABLENAME}.do?JSONv2&sysparm_action=insert

https://{INSTANCENAME}.service-now.com/api/now/import/{TABLENAME}

The data is being pushed to the REST web services from INFORMATICA.

The problem is that many of the records to not successfully get loaded.

Multiple loads of just over 100 records would yield 35 or 36 records loaded.

How would you troubleshoot this from the ServiceNow side?

I have tried looking at the transaction logs but I don't see any of their REST transactions.

I have also attempted to enable the glide.rest.debug system property by setting it to true, though I haven't figured out how to view the logs as I don't see anything being logged in the system logs.

Thoughts?

[Jace Benson]

Right now the only way to get all the logs is to download teh node logs for each node and grep what your are looking for.   It sucks.  

[John VanBruggen · Accepted solution]

So, apparently starting with FUJI that answer resides in this:   developer.servicenow.com/app.do#!/document/content/app_store_doc_rest_integrate_fuji_r_DebuggingRESTQueries?v=fuji

[tony_barratt]

Hi John,

Yes, you are right, after Fuji you can debug using glide.rest.debug.

Info on this is mentioned on developer.servicenow.com in the link you supply.

it is also described here on the ServiceNow wiki:

REST API - ServiceNow Wiki

Best Regards

Tony

[Jace Benson]

Still says it has performance impact