06-26-2019, 01:18 AM
Hi again,
after checking your data, seems that several "ghost" sessions have the same IP address and browser as the real sessions.
So, I'm guessing that, somehow, another request from the same source is causing a new session to be created (and stay alive even when the real session ends)... If that is happening, the LogSessionEvents switch should be enough to identify which request is triggering this
after checking your data, seems that several "ghost" sessions have the same IP address and browser as the real sessions.
So, I'm guessing that, somehow, another request from the same source is causing a new session to be created (and stay alive even when the real session ends)... If that is happening, the LogSessionEvents switch should be enough to identify which request is triggering this