The Session Log Function got a revamped look – Come see what’s Changed

Welcome Readers,

Today I have more of an update then something new to show you all. It was pointed out to me by a colleague of mine, that the Session log Function (AKA, the global engine trace that’s under Administration, Usage section) has changed in Version 12 Patch 27. It’s been redone, per say, into a newly updated function called X3 Session Log. It still does relatively the same function, but it now has an added tracking option for you to see what you have traced previously. What I mean by that is this:

Old function

New function


You can see that there’s this added layer for tracking like a history of what you have ran.

It still gives you the same options plus a couple extra like “memory usage” and “file access time” which I don’t recall being previous options for the engine trace.

Anyways, we are going to take a quick peek at what’s there so those who are not on patch 27 yet can see what’s up.

On the main screen you will now have to click New X3 session log from the right list to actually start logging. More or less, you will create a log record for tracking.

This will take you to the next part where you then have to label your log and define the levels. The levels are the old numbering system we used to use for the engine tracing like selecting 1 or 2 or combining for stuff like 5 (which was 2 and 3 logs).

Here’s a look at what the levels has to select from


So now, instead of adding the value numbers together and putting that total into a field, you can now just check off what you want the engine trace to log and it automatically adds them to the logging.

When I add one selection

When I add a second selection

I added SQL logging (4) to 4GL logging (2) and you can see that it adds them to the levels digest as 6 (2+4).

Once you fill out all the values you want, click save to save it.

After you click save, the right list should change to give you the option to enable the log and refresh the log.


When you click on enable x3 log it should automatically check the enabled button and change the button to disable x3 log

So, the logs are still saved to the Main runtime folder in the log directory. Even though you can schedule them now in the administration module, you unfortunately still have to go to the runtime logs folder to get a copy of the logs.

And that about wraps up this topic.

On a side note: in the same X3 session logs they added additional types that we will explore more later this quarter.

You can see that the engine trace now has other options as well, not just runtime session related.

Next time we can explore how some of these work, so keep a look out for more topics on X3 session tracing and logging.