Not seeing debug output

[peterraeves]

I had seen debug output with one client, so I tried to use 'gs.debug' myself, but I do not see any output?

I did notice the property 'glide.amb.log.level', which is set to 'info', but I'm not sure whether that's the culprit. Especially as I cannot decrease that value to 'debug' as it is maint only. Anyone any ideas?

[peterraeves]

Yes. It works. That's the one I'm using now...

[HarshTimes]

Yes, but if you will try gs.log in scoped application, it will not work. You can say that gs.log is a legacy.

[Shishir Srivast]

The debug messages are printed only when in debug mode or when session debug for that application is enabled. You should try out the scoped Logging API by printing with gs.debug() in your business rules and script includes, and enabling session debug in the UI.

scope_name.logging.verbosity

Configures log verbosity: error, warn, info, or debug. Type: String Default value: info Location: System Property [sys_properties] table

Reference: http://wiki.servicenow.com/index.php?title=Scoped_Script_Logging#gsc.tab=0

[peterraeves]

As I told earlier. I am not in a scoped app and I want the output to create a record in the log table...

[Martin138]

Hi Peter,

Did you find a solution to this issue? I have the same question!

I've tried to create two different system properties "logging.verbosity" and "global.logging.verbosity" and set the value to "debug", but without any luck.

BR,

Martin