Inbound HTTP Request logs

[Simon Sparke]

I'm aware you can pull the Node logs to view inbound HTTP requests & results, but this IS NOT a great design to debug integrations in ServiceNow. (especially in Production environments)

ServiceNow has an "Outbound HTTP Requests" log table.

Why isn't there be an "Inbound HTTP Requests" log table?

Seems logical to me? Or am I missing something here?

[johnmuenste]

Hi Simon,

I do not have a solution for out of box API's, however when building custom APIs I insert a record on a custom table any time the API is called. That way I can keep track of how my APIs are being utilized and log any information for troubleshooting.

[Simon Sparke]

Hey John,

Yeah thats a good susggestion, its definitely helpful whilst building a custom API.
Its just a shame you can't extand OOB API's to log against your custom as well

Thankyou for the suggestion though

[Erik Stolberg]

You can use the syslog_transaction table to view incoming REST. Add a filter for the "Created By" if you know the user making the call (or IP Address if known), and Type=REST. The URL field will contain the Endpoint being hit.

Notes:

• if parameters are not showing in this URL field, check to make sure that the table being called is not listed in the property "glide.parameter.dump.table_denylist" as this will cause the parameters to be redacted.
• the body of the request is not logged via this process, so this is best for REST calls that are only using URL paths, filters, or query string parameters and not via the body or header