Idea ID 2782173
With Service Now RITM fulfillment integration, Service Now returns the REQ# it generates back to IG. With the logging level on Trace or Debug, you will see this in the log file. You also see a lot of other data on fulfillments which adds additional overhead to the system. Would like a more granular logging that would include the REQ# to be logged without all the overhead of using Trace or Debug level. Basically to have the same logging as Info but also to include the REQ# that Service Now sends back to IG.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.