Hi all,
In this post, I would like to explain how Pulse stores TM1 sessions.
One of the most popular features of Pulse is its ability to monitor IBM Planning Analytics (TM1) sessions. By default, Pulse captures all TM1 sessions every second. When you open the Pulse Live Monitor, you can view all active TM1 sessions.
The real advantage of Pulse is not just seeing the active sessions in real-time, but also being able to look back and check who was using your TM1 application at any given time.
To report on TM1 sessions, Pulse offers several features. Below, we explain how to view TM1 sessions by feature:
TM1 Sessions in the Live Monitor
Sessions in the Pulse Live Monitor are the sessions that are happening right now (Who is currently logged in to TM1). The Pulse App Server asks TM1 each second (by default) to send the sessions and threads to Pulse. Then Pulse will show this data in the Live Monitor. Each second this should be updated with the latest sessions.
TM1 Sessions in the Report/User Sessions
The sessions you see in the User Sessions are stored in the Pulse database (table called Sessions). A session will be stored in the Pulse database only if it has logged off and if the session was more than 60 seconds.
What you see in the User Sessions table can be seen in the Pulse database. If your customer is using the default h2 database, you can use the console to see the table, more information is available in the following article: Connecting to the Pulse Database - Cubewise CODE
TM1 Sessions in the Pulse Explorer
Pulse stores TM1 sessions in two indices:
- pulse-server-state: This index contains all TM1 sessions, similar to what you see in the Pulse Live Monitor feature. Since all sessions are stored, this index grows quickly. By default, Pulse retains only two months of pulse-server-state data.
- pulse-tm1-session-history: This index shows the same data as the Report/User Sessions feature, but only includes TM1 sessions that were active for more than 60 seconds. The advantage of this index is that it stores less data, allowing for a longer retention period. By default, Pulse retains one year of TM1 sessions in this index.
It’s important to note that you cannot reconcile the data between these two indices. Although both store TM1 sessions, the pulse-server-state index will contain more sessions than the pulse-tm1-session-history index.
I hope this helps,
Cheers,
Vincent