It would be nice if we could insert a custom "Marker" from the Service Console into the current log file so it can be used as a reference point later on. This would be helpful when troubleshooting issues.

Uomo,

If you use a Run Script action, you can use the command Watch.log to have a custom message inserted in the log file, so this could be used to make those markers. Syntax is:

Watch.Log Message(string), ErrorType(integer)

The message is a string that will be your message. The ErrorType is a number that will determine the color which will be used for the message if you look at it in the service console. Possible values:

1: Red
2: Orange
3: Black
4: Grey

Example for a vbscript command:

Watch.Log "This is a custom error message.", 1

When the Run Script is run, "This is a custom error message." will appear in the log, and in the service console, it will appear in red.

Hope that helps!

Regards,
Raphaël Lalonde Lefebvre

I am doing this currently, but when debugging the ability to simply insert a line into the log file from the console would be convienent.

Flagging a position in the log file from the console may be a better method to express what I'm looking for. That and a more robust means to filter out processes that you are not currently debugging.

On sites with a lot of activity it is often difficult to troubleshoot using the console because multiple processes keep moving the contents. Even though you can pause, often I need to see just what I'm looking for.

The ability to place a flag or custom marker allows me to quickly identify where new items are happening or a time period.