Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

How to identify direct web service calls made to Servicenow

rachanar
Tera Contributor

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

5 REPLIES 5

Stefan Baldhof1
Kilo Guru

Hi Rachana,



have a look at the transactions log, type "SOAP" and "REST". You should find all necessary information there.



transactions.png



transactions_list.png



Regards,


Stefan


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


JC Moller
Giga Sage

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.267Infohttp-46Session created: D4054AE90F3CB200CF9A8B9AE1050E6F, timeout after 30 minutes of inactivity
06:21:51.777Infohttp-43New transaction D4054AE90F3CB200CF9A8B9AE1050E6F #7713 /incident.do
06:21:53.626InfoDefault-thread-182D4054AE90F3CB200CF9A8B9AE1050E6F

#7713 /incident.do Parameters -------------------------


XML=



06:21:53.867InfoDefault-thread-182D4054AE90F3CB200CF9A8B9AE1050E6FStreamingUnloader unloaded 58 records to xml
06:21:53.869InfoDefault-thread-182D4054AE90F3CB200CF9A8B9AE1050E6F#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


Hi,



And there is off course also the REST & SOAP API Analytics -dashboard, which gives you a lot of additional information about the SOAP and REST resource usage on your instance.



- Jan



Soap.jpg