I have some question from client to clarify. In general, RUM Sessions are timeouted after 30 mins of inactivity, 200 user actions or after executing dtrum.endSession(). I’m talking about concurrent sessions count, not about licensing case here.
Our client sees some differences (6-10%) between RUM users count and their measures on Database (for example). The question is if there are any extra criteria that does not exist in documentation that may be reason of session timeout. Can we change default behavior somehow? Client needs this measure to be more accurate.
Answer by Julius L. ·
One of the reasons I can think of are sessions where RUM JS is not even injected (typically when users are running ad blockers). Your difference (6%-10%) is low and might be a result of different measurements (Dynatrace vs application itself).
Can you instead measure of service requests that would indicate for example a successful login? (that will result in a session).
Salesforce integration with Dynatrace 3 Answers