IMPORTANT ANNOUNCEMENT

These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#41498 - 11/26/12 03:45 PM Better Logging
venatic Offline
OL Newbie

Registered: 09/08/11
Posts: 11
Having the ability to create logs based on a Process would be quite beneficial and then to choose how verbose each of these logs is. Lets say I have 100 processes on a server, I would like to be able to have 1 of these processes have its own log file separate from all the rest of the processes.

Top
#41503 - 11/27/12 09:25 AM Re: Better Logging [Re: venatic]
Raphael Lalonde Lefebvre Offline
OL Expert

Registered: 10/14/05
Posts: 4956
Loc: Objectif Lune Montreal
venatic,

To be honest, while there is no setting to configure logs for each individual processes, there is a hidden setting that you can enable to have ALL individual processes get their own log file. You can go to Workflow's Preferences, under General, then press CTRL+Alt+Shift+F12 at the same time, and it will enable an option called "Log all process events at the same time in separate log files", which will enable individual logs for each processes, in addition to the regular logs.

Why is it hidden you might ask? Well, while this option can be interesting in certain cases, there are also many problems with it:
- Having so much logging will have an impact on performance(especially with 100+ processes), as all logs would keep getting bigger and bigger, and for every actions, something gets written in all of them. It has to go through these entire files to write each events, so do this 100 times for every events, and it will affect performance a lot.
- Consequently, these log files can quickly reach huge file size and could fill a lower capacity hard drive.
- Having log files too big, or if your hard disk becomes full, could cause errors and jobs will fail.

So while it's an interesting option for debugging purposes, it's dangerous to put in production, which is why it's hidden by default.

Note that as this is a hidden setting, this isn't something that we officially support, and we will not be able to help you if problems occurs while this setting is turned on. Use it at your own risks.

Regards,
Raphaël Lalonde Lefebvre

Top
#41506 - 11/27/12 10:56 AM Re: Better Logging [Re: Raphael Lalonde Lefebvre]
venatic Offline
OL Newbie

Registered: 09/08/11
Posts: 11
Sounds interesting, I am glad I have a test server!

Top
#41508 - 11/27/12 12:17 PM Re: Better Logging [Re: venatic]
venatic Offline
OL Newbie

Registered: 09/08/11
Posts: 11
This did some interesting things but not what I am looking for.

I would still like an enhancement to be able to have only certain processes have their own log file.

Top
#45355 - 11/06/13 09:01 AM Re: Better Logging [Re: venatic]
Uomo Del Ghiaccio Offline
OL Expert

Registered: 02/21/01
Posts: 669
I have several customers who have requested this. I've skirted the issue by writing my own log file if necessary. Having the option to configure a specific process to create a seperate log file would help in these situations and when debugging. Even if it left the entries in the regular log and simply extracted items related to a specific process or group of processes.
_________________________
Uomo Del Ghiaccio
--------------------

Top
#51310 - 04/03/15 01:41 PM Re: Better Logging [Re: venatic]
Uomo Del Ghiaccio Offline
OL Expert

Registered: 02/21/01
Posts: 669
Perhaps adding in some more robust filtering similar to Procmon so you can filter for the specific process you are looking for?
_________________________
Uomo Del Ghiaccio
--------------------

Top