Programmatic control over logging in TI / Chores
Posted: Tue Mar 18, 2014 10:04 pm
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
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