-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-47389: app metrics #387
Conversation
52697e2
to
88ac4a8
Compare
88ac4a8
to
8549523
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not seeing metrics for the lab spawning process, just for notebook execution. Can we get those as well? I think those are going to be really important. (I don't care about metrics for login and certainly not about the intentional pauses, or for things like creating a web socket.)
Yeah, good call, this is probably one of the most useful events we can have! I added |
579a94a
to
7b39065
Compare
I'll bring up in co-work whether we want to replace the current timing stuff with sampled Sentry tracing. If we do decide to do that, we may not want some of these as analytical metrics. Notebook cell executions for example, I don't see the value in keeping that data forever, but I do see the value in keeping it short-term to debug why an entire notebook is suddenly slow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thanks! I'm fairly sure that there are ways to make some of this code simpler, or at least with somewhat sharper separation of concerns, but I think that's an orthogonal refactoring to the work you're doing, and as you say we should probably wait until we've integrated Sentry and then see what the remaining complexity looks like.
bc86c8c
to
4601389
Compare
Publish app metrics events.
Phalanx support