Hi,
While I’m building reports using the pulse-tm1-session-history-* index what I’m noticing (in two different clients with several hundred users) is that the Context is empty a lot (55% in one client 89% in another).
select
ServiceName,
DisplayName,
IsAdmin,
LogInTime,
LogOutTime,
SessionTime,
CommittingCount,
RunningCount,
WaitingCount,
RollingBackCount,
UserWaitingCount,
LogCount,
Product,
Context,
Name,
ThreadId,
Id,
timestamp
from
pulse-tm1-session-history-2025
where
DisplayName = 'Blalx012'
and timestamp BETWEEN '2025-09-12 17:20:00' AND '2025-09-12 23:59:00'
order by timestamp desc
This pattern repeats a lot, one session has a Context but a new one which start before the prior one ends, has no Context.
Then I started looking at the pulse-server-state-* index to see what was happening:
select
DISTINCT(SessionId),
Context
from
pulse-server-state-2025-09
where
DisplayName = 'Blalx012'
and timestamp BETWEEN '2025-09-12 17:20:00' AND '2025-09-12 23:59:00'
order by timestamp desc
So it seems that during the same time period only 3 sessions were created by that user but the sessions got “re-contexted” to another client by updating the session header. I’m assuming this happens when PAFE and PAW share the session cookie, but I have no idea.
That aside, it does not seem that Pulse can deal with this when it comes to registering these events in the ‘pulse-tm1-session-history-*’ index as it creates a new document per changed context.
What are your thoughts?
Cheers!
nico