Alert Types

Pulse for TM1 enables you to create alerts so you can proactively manage your TM1 server. To create alerts go to Administration --> Alerts, below is a full list of all the alert types that are available:

  • Offline: The TM1 instance cannot be contacted, this normally means the instance has not been started, has been stopped or has crashed. Use this alert to be notified when ever your TM1 instance becomes unavailable.
  • Memory: The memory used by either the server or instance of TM1 has exceeded the threshold specified (% of memory use). Leave the instance field blank to set the alert for the whole server.
  • CPU: The CPU used by either the server or instance of TM1 has exceeded the threshold specified (% of CPU used). Leave the instance field blank to set the alert for the whole server.
  • Concurrent Users: The total number of people logged into TM1 at any point of time exceeds the number provided.
  • Waiting: The number of users in a wait state, normally caused by a TM1 object being locked by another user, exceeds the threshold.
  • Wait Time: The maximum amount of any user has been waiting (i.e. in a wait state as above) exceeds the threshold (seconds).
  • Error Log: Attaches any error logs generated when a chore or process is executed. Your can filter by then name of the error log (which contains the process name that generated the log) using wildcards (*).
  • Disk Free: The available disk space (GBs) for a drive has dropped below the threshold. You can create different alerts for each drive by enter the drive letters separated by commas, i.e. C,D.
  • Run Time: The amount of time (seconds) that any one thread has been executing for (run state) has exceeded the threshold.
  • Message In Log: Text in the TM1 Message Log (tm1server.log) matches the wildcard specified in the alert. This can be used for many purposes such as: when a chore/process completes, a rule becomes invalid, the TM1 instances becomes available, etc. Look through the tm1server.log file for the text generated when these events occur.
  • Process Run Time: Is triggered when a process runs longer than the average by the value specified (%). You can filter the processes this is triggered on using the process name and wildcards (*).
  • Chore Run Time: Is triggered when a chore runs longer than the average by the value specified (%). You can filter the chores this is triggered on using the chore name and wildcards (*).
  • Cancel Thread: Cancels a thread automatically that has exceeded the specified amount of time (seconds). You can also filter the alert so that only particular functions are cancelled, such as ViewArrayConstruct