Alert Types

Pulse for TM1 enables you to create proactive alerts to monitor and manage your TM1 environment. To create alerts, go to Administration → Alerts.

Available Alert Types

Offline

Triggered when a TM1 instance cannot be contacted — typically because it has not been started, has been stopped, or has crashed. Use this alert to be notified whenever a TM1 instance becomes unavailable.

Memory

Triggered when the memory used by either the server or a specific TM1 instance exceeds the configured threshold (as a percentage of total memory). Leave the instance field blank to apply the alert at the server level.

CPU

Triggered when the CPU usage of the server or a specific TM1 instance exceeds the configured threshold (as a percentage of CPU used). Leave the instance field blank to apply the alert at the server level.

Concurrent Users

Triggered when the total number of users logged into TM1 at any one time exceeds the configured number.

Waiting

Triggered when the number of users in a wait state — typically caused by a TM1 object being locked by another user — exceeds the configured threshold.

Wait Time

Triggered when the maximum time any single user has been waiting (in a wait state) exceeds the configured threshold in seconds.

Error Log

Attaches any error logs generated when a chore or process is executed. You can filter by the name of the error log (which contains the process name that generated it) using wildcards (*).

Disk Free

Triggered when the available disk space (in GBs) for a drive drops below the configured threshold. You can create separate alerts for each drive by entering drive letters separated by commas (e.g., C,D).

Run Time

Triggered when the time (in seconds) that any single thread has been in a running state exceeds the configured threshold.

Message In Log

Triggered when text in the TM1 Message Log (tm1server.log) matches the wildcard pattern specified in the alert. This can be used to detect when a chore or process completes, a rule becomes invalid, or the TM1 instance becomes available. Review the tm1server.log file to identify the relevant text strings.

Process Run Time

Triggered when a process runs longer than its historical average by the configured percentage (%). You can filter which processes trigger this alert using the process name and wildcards (*).

Chore Run Time

Triggered when a chore runs longer than its historical average by the configured percentage (%). You can filter which chores trigger this alert using the chore name and wildcards (*).

Cancel Thread

Automatically cancels any thread that has been running longer than the configured time threshold (in seconds). You can optionally filter so that only specific functions are cancelled, such as ViewArrayConstruct.