Tm1s-log.properties file
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Tm1s-log.properties file
Does anyone know of a document that lists all the options that can be used in the tm1s-log.properties file? I have made several requests to IBM for this and all they keep sending me back is a link to the documentation that only shows what is in the sample file. I know there are dozens of options that can be set but I can't find what those options are anywhere. BTW, I am not talking about the file name or amount of memory used for the log file. I'm talking about the settings that control which events actually trigger an entry in the log, like successful login, TI process executing, MDX errors, etc.
- gtonkin
- MVP
- Posts: 1261
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: Tm1s-log.properties file
Hi Tom,
Have a look at the post here
Adding
to an existing logger or tweaking it to write to its own should dump the available options. I have not tested recently though.
Have a look at the post here
Adding
Code: Select all
log4j.logger.TM1.MetaLogger=DEBUG
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Tm1s-log.properties file
Thanks for the help. I had initially tried that and it didn't work (we're on the IBM Cloud) but I went back and removed everything except that statement and I got the list. Now to figure out what all those options actually do. 

- gtonkin
- MVP
- Posts: 1261
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: Tm1s-log.properties file
That is the challenging part - cannot find any documentation and depending on the issues, we generally enable one parameter, monitor, change it if nothing useful yielded etc. Black-box/trial and error.
I am sure that you are very aware but mentioning in case others hit this thread in the future:
Using DEBUG can generate huge files rapidly. Make sure you have lots of disk space and watch the file closely.
If you do find anything useful, please share. Good luck on your quest.