Simplify session events and heartbeats

[exceptionless]

Simplify session events and heartbeats

[niemyjski]

I think we could make this a lot better but it will take some feedback and playing around. I do wish we would store some kind of guid (session storage) or user id (local storage) and when the client loads up look at that and auto start submitting heartbeats? I think that would solve a lot of this, but do we do that once you call useSessions()? The problem with storing a user id or guid is that once the user is authenticated we currently have no way to merge the two sessions. So it would almost have to be two different sessions, or we create a job that updates existing events with new session user (but you might want to see that they were a anon user).

Also, the .NET client has a internal session identifier that gets set to either the user specified session id or the current user and we look at that when submitting. What do we do when the user calls SubmitSessionEnd? Should we clear that and the default user stored in configuration?

Also, when we get to submitting page views, I think a lot of these issues will go away, one shouldn't need to do much to get value out of the system and it's not currently clear to end users that they shouldn't be needing to submit a session start event (only when the user logs in, I know a session might be long lived),

[niemyjski]

Did you ever find a better solution for this?

[niemyjski]

@srijken I think this is much better solved in the new version, please let me know if this is not the case and we can reopen and work to improve this.

I would do the following for session management:

import { Exceptionless } from "@exceptionless/browser";

await Exceptionless.startup((c) => {
  c.apiKey = "MY_API_KEY";
  c.setUserIdentity("12345678", "Blake");
});

await Exceptionless.submitSessionStart();

One could argue we would need to make session end submission easier via browser lifecycle events.