Pulse User Sessions vs. REST API User Sessions

Pulse Pulse Questions
, , ,
1

Hi pulse Team,

we have a situation here, where pulse is showing different information about the User-Sessions in TM1 then the TM1 REST API.

Which version is true?
Is this a known issue?

Cheers,

Marius

Postman.PNG671Ă—559 21.8 KB
Pulse.png1071Ă—810 19.7 KB

2

Hi @mwirtz,

Sessions and Threads are different things, using the old C API every “session” had its own thread for the lifetime of the session. For the REST API this has been changed so that TM1 holds a list of “sessions” separate to the threads and then shares the threads between the sessions. This new model only impacts REST API connections and should help when scaling to many thousands of users.

Pulse is getting information through the old C API but it should be similar to what you receive see when querying the Threads collection in the REST API.

1 Like
3

Hi,

Yes. When we query Threads through the REST API we get a very similar picture to what pulse is showing.

I think it would be nice if in a future version of Pulse you could toggle whether you want to see Sessions or Threads in the monitoring page.

4

Hi @mwirtz,

You can tick the Active box to remove all inactive sessions:

image.png1092Ă—333 9.41 KB

Cheers,

Vincent

5

Hi,

we are still on Pulse 5.5. In our Version Pulse is showing Threads, even though in the page it says “Session Monitor”.
(As Tim pointed out in his earlier response, the naming makes sense kinda, because there used to be a 1 to 1 relationship between session and thread in TM1 versions < 10.2.2)

In the TM1 Server (>= 10.2.2) a user can have a pool of threads associated to their session.
What I was looking for is an overview of the sessions that are curently open in TM1, because in our Setup the monitoring page looks a bit busy / obscure as we have a lot of REST API sessions, which all have 1 or more threads associated to them (sometimes up to 10).

Not sure if the Active Checkbox could help. The Active Checkbox is still Filtering Threads in Pulse 5.6, right?

Cheers,

Marius

6

Hi @mwirtz,

Pulse only shows threads, Pulse has been around longer than the REST API and thread/session were the same thing for the first 30 years on TM1. We will look at adding the session info when we migrate to the REST API.

7

Okay. Thank you

8

Hi,
even though this situation has existed for a while now users are still bothered and irritated by the “wrong” number of users that is displayed in Pulse.

Instead of displaying “wrong” information it would be better if pulse does not display the number of users (or if the users tab are greyed out).
Please consider this proposal for the next Release / Hotfix.

Cheers,

Marius

grafik

9

Hi @tryan,

This is becoming a very common issue now with everyone moving to PA, have you considered fixing this in Pulse v5?

10

Hi @prajtar,

This is a limitation of the C API that Pulse 5 and earlier uses. We are in the process of moving to the REST API, it is unlikely there will be a fix for 5.x versions.