How to identify direct web service calls made to Servicenow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 03:53 AM
Hello Everyone,
Is there any table/any way where we can track or see all the direct web service calls made to Servicenow.
We have a requirement where this tracking is required.
Any help or details on this is much appreciated.
Many Thanks,
Rachana
- Labels:
-
Integrations

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 04:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 04:21 AM
Hi Stefan,
Thank you for the details.
I did check the Transactions table before putting up this question.
The problem is, say for example - an user access - https://<instance_name>/incident.do?XML, I was not able to find any corresponding entry in transactions table.
Would you please provide some details on this.
Thanks,
Rachana
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 07:02 AM
Hi,
I believe the only place where you can view more details on XML data retrievals is the localhost log.
Wiki says:
"The ServiceNow platform supports programmatic retrieval of XML data through a URL query (HTTP GET request). The request is triggered by use of a URL parameter."
In the log you have these lines:
06:21:47.267 | Info | http-46 | Session created: D4054AE90F3CB200CF9A8B9AE1050E6F, timeout after 30 minutes of inactivity | |
06:21:51.777 | Info | http-43 | New transaction D4054AE90F3CB200CF9A8B9AE1050E6F #7713 /incident.do | |
06:21:53.626 | Info | Default-thread-182 | D4054AE90F3CB200CF9A8B9AE1050E6F | #7713 /incident.do Parameters ------------------------- XML= |
06:21:53.867 | Info | Default-thread-182 | D4054AE90F3CB200CF9A8B9AE1050E6F | StreamingUnloader unloaded 58 records to xml |
06:21:53.869 | Info | Default-thread-182 | D4054AE90F3CB200CF9A8B9AE1050E6F | #7713 /incident.do -- total transaction time: 0:00:02.091, transaction processing time: 0:00:00.253, total wait time: 0:00:01.838, session wait: 0:00:01.838, semaphore wait: 0:00:00.000, source: 82.118.214.3, chars: 10,645, uncompressed chars: 0, SQL time: 5 (count: 5), business rule: 0 (count: 1), phase 1 form length: 0, largest chunk written: 512, request parms size: 56, largest input read: 0 |
- Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2017 07:27 AM