How to use gs.log

[Mohammad8]

I have a Scheduled Job in which I want to add a simple log message. All the article say that I can simple write gs.log("my message"); and this should work. Unfortunately, when I go to the sytem log, I don't see my log message.

[Anurag Tripathi]

I mostly use gs.log('message', 'source'); //source here can be any string that makes it easier to find the logs or report on them if needed.

In the log table the  i add a filter for all logs created for the source i added and created in the last 15 mins. this givesme a refined list and dont have to go finding my log in  a whole pile of messages that are not useful for me.

[Community Alums · Accepted solution]

You can mention a source that will be populated in the 'Source' field in the log record. You can search using the value in the 'Source' field.

Else, you can try using gs.info('message','source'). This will also add a log record in the sys_log table.

[Mohammad8]

Thanks. gs.info worked for me

[Harsh Vardhan]

i am just adding one point here.

do you know why gs.log() did not work?

just because your are working on scoped application and that's why gs.info() worked .

if you see my response which i had response earlier and mentioned this scenario.

happy to help you.

[Priyanka Gupta]

Hi Mohammad,

System logs are always flooded with multiple logs. If you want to identify the log you are looking for,

1. Go to System Log -> All. 
2. In the Message, search for *<your message>. Don't forget the * here.

When I am debugging something, I generally write-

gs.log("---------------------> my message")

Since there is a big arrow here, it is easy to identify in your logs. However, I wouldn't recommend doing this if you are putting a permanent log in your job. In that case, you should write-

gs.log('message', '<your message here>');

You can again use the search technique to search for your log.

Hope this helps!

Please mark my answer correct/helpful based on the impact.

Priyanka