Programmatic control over logging in TI / Chores

Suggest and discuss enhancements for TM1
Post Reply
User avatar
Steve Rowe
Site Admin
Posts: 2410
Joined: Wed May 14, 2008 4:25 pm
OLAP Product: TM1
Version: TM1 v6,v7,v8,v9,v10,v11+PAW
Excel Version: Nearly all of them

Programmatic control over logging in TI / Chores

Post by Steve Rowe »

I'd like to be able to conditionally turn TI logging in the TM1 message log off or on a case by case basis in the TI itself.

We are using PI to export and load data using 20 chores that are scheduled to run every 30 seconds. These chores only do work around 8 times a day when other TIs interacts with a schedule cube set various flags that indicate to the chores that there is work to do. This works v well and we are able to rapidly process data and minimise the read lock when loading data into the cube. We have not been able to note a performance down side to having the chores set-up like this.

Of course having 20 chores running every 30 seconds means that the message log fills up very quickly and it becomes very hard to impossible to use the message log, especially if we have to activate any enhanced DEBUG logging.

So in the TI that underlies the 20 chores I'd like to be able to only activate the logging when the TI reaches the point that it determines that is has work to do.

Cheers,
Steve R
Technical Director
www.infocat.co.uk
User avatar
Alan Kirk
Site Admin
Posts: 6606
Joined: Sun May 11, 2008 2:30 am
OLAP Product: TM1
Version: PA2.0.9.18 Classic NO PAW!
Excel Version: 2013 and Office 365
Location: Sydney, Australia
Contact:

Re: Programmatic control over logging in TI / Chores

Post by Alan Kirk »

Steve Rowe wrote:I'd like to be able to conditionally turn TI logging in the TM1 message log off or on a case by case basis in the TI itself.
Agreed with this one as well; the logs are way too chatty (charitable description) / bloated (accurate description) in the newer versions. While we're at it I'd like to expand this one step further with a TI variable named something like WriteErrorLogsOnlyInErroringProcess.

When I'm calling process execution, particularly when the calls are a few levels deep, I really don't need all of the:

Code: Select all

Error: Prolog procedure line (97):  Errors occurred during execution of process "MyCalledProcess".  Check error log file for that process for more details
logs. It bloats my log files folder, and worse than that it obscures the presence of the files that really do contain the relevant information.

I understand why the messages are written and the reason isn't brain-dead, but it's still something that isn't always useful (in fact I've never found it useful) and should certainly be able to be turned off so that when you look in the log directory, all you see are the error logs that contain the error information, and not a profusion of logs that merely point you to other logs. Or, to put it another way, "Don't bore us, get to the chorus".
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
John Zhang
Posts: 9
Joined: Tue Jan 05, 2010 4:09 am
OLAP Product: TM1
Version: 10.1
Excel Version: 2007
Location: Hong Kong

Re: Programmatic control over logging in TI / Chores

Post by John Zhang »

Exactly what we need in our environment as well. Meanwhile is there any workarounds available before TM1 evolves to that capability? Thanks.
User avatar
jim wood
Site Admin
Posts: 3951
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: PA 2.0.7
Excel Version: Office 365
Location: 37 East 18th Street New York
Contact:

Re: Programmatic control over logging in TI / Chores

Post by jim wood »

I can understand why they've done what they have this, but for me you should have the ability to control all levels of logging. I get the fact that's it's handy for bugs or identifying process issues but the level of logging needed can chnge per user company, so the level of logging should reflect this.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
BrianL
MVP
Posts: 264
Joined: Mon Nov 03, 2014 8:23 pm
OLAP Product: TM1
Version: 9.5.2 10.1 10.2 PA2
Excel Version: 2016

Re: Programmatic control over logging in TI / Chores

Post by BrianL »

jim wood wrote:I can understand why they've done what they have this, but for me you should have the ability to control all levels of logging.
You can set TM1.Process=OFF to disable these messages entirely.

I'm not sure how a TI could selectively enable/disable log messages that have already been output (Process "foo" executed) since that message is logged BEFORE the TI script has actually started executing.
Post Reply