By Sanjeev Datta, Consultant for PerformanceG2
There are multiple ways of monitoring the performance of TM1 using built-in tools. In my 4-part, weekly blog series, I will be discussing some of these tools including: Message Logging, Control Cubes, TM1 Top Utility and Performance Counters.
For part 1 of my series this week, I will be discussing Message Logging:
Message Logging
There are 4 internal logging files which act as “flight recorders” for the TM1 Server and can help in tracking changes made to the server. These 4 internal logging files are:
Admin Server Log: The TM1 environment is a client-server environment. As the TM1 server starts up, they register themselves with the TM1 Admin Server. The TM1 clients contact the Admin Server to find the location of all available TM1 Servers. SSL security is established between TM1 Admin Server, TM1 Client Server and TM1 Server. The log data can then be used to track the various Server startup times and the connection with the Admin Server.
Transaction Logs: These logs acts as a “User Audit Log” where all changes made to the data transactions are recorded along with a time stamp. Developers can use this log file to identify any changes made to the data by Users, Client Machines, Cube Name, Element Type and cell number. The level of detail allows to store the before and after numbers as well.
Server Message Log: This log file maintains details performed by the server such as executed processes, chores, loaded cubes and dimensions, and synchronized replications.
Audi Log: The Audit Log records any changes to TM1 objects. Login activities and modifications to dimensions, views and subsets, are all captured in this log file.
Check back next week for part 2 of Performance Monitoring with TM1 blog series where I will be discussing Monitoring Server Performance Using Control Cubes.
