-
Notifications
You must be signed in to change notification settings - Fork 28
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
Emit telemetry events on success and failure of the Create Job, Create Job Definition, Create Job from Job Definition hooks #472
Emit telemetry events on success and failure of the Create Job, Create Job Definition, Create Job from Job Definition hooks #472
Conversation
Co-authored-by: Piyush Jain <[email protected]>
Co-authored-by: Piyush Jain <[email protected]>
Co-authored-by: Piyush Jain <[email protected]>
@3coins thank you for looking into this, implemented your comments re not logging an |
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.
"Unknown error occurred" is a generic message, but it may not inspire confidence. Do we have any idea about what sorts of errors might trigger the generic message? If so, can we provide any additional guidance? Something like, "An error occurred. Please try again."?
@JasonWeill thank you for looking into this. Any error / error object that does not have fields expected from es5 Error object would trigger the generic error message. Most probably to occur are connection failures, connection timeouts, third-party libraries throwing something else than es5 |
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.
Looks good, thanks!
…e Job Definition, Create Job from Job Definition hooks (#472) * add job/job definition creation event success or failure logging * fix create-job logging format * log error message and httpStatusCode when error occurs * Update src/index.tsx Co-authored-by: Piyush Jain <[email protected]> * Update src/context.ts Co-authored-by: Piyush Jain <[email protected]> * Update src/context.ts Co-authored-by: Piyush Jain <[email protected]> * log string for logDetails, not whole error * catch errors as unknown, not Error * Make generic error message more user-frinedly and actionable per @JasonWeill --------- Co-authored-by: Piyush Jain <[email protected]>
…e Job Definition, Create Job from Job Definition hooks (jupyter-server#472) * add job/job definition creation event success or failure logging * fix create-job logging format * log error message and httpStatusCode when error occurs * Update src/index.tsx Co-authored-by: Piyush Jain <[email protected]> * Update src/context.ts Co-authored-by: Piyush Jain <[email protected]> * Update src/context.ts Co-authored-by: Piyush Jain <[email protected]> * log string for logDetails, not whole error * catch errors as unknown, not Error * Make generic error message more user-frinedly and actionable per @JasonWeill --------- Co-authored-by: Piyush Jain <[email protected]>
…e Job Definition, Create Job from Job Definition hooks (#472) (#475) * add job/job definition creation event success or failure logging * fix create-job logging format * log error message and httpStatusCode when error occurs * Update src/index.tsx * Update src/context.ts * Update src/context.ts * log string for logDetails, not whole error * catch errors as unknown, not Error * Make generic error message more user-frinedly and actionable per @JasonWeill --------- Co-authored-by: Piyush Jain <[email protected]>
Emit telemetry events on success and failure of the Create Job, Create Job Definition, Create Job from Job Definition hooks.
body.name
string is now following a new convention:org.jupyter.jupyter-scheduler.SOURCE.EVENT[.STATUS]
(vs old conventionorg.jupyter.jupyter-scheduler.SOURCE.EVENT
) whereSTATUS
is either"success"
or"failure"
CreateJob
now emits"create-job"
or"create-job-definition"
forEVENT
instead of just"create"
depending on if job or job definition is being createdbody
now has optionaldetail
parameter storing error message (or other string with event detail)unknown
type and using type guarding instead of assuming all errors caught would be ofError
type (ts runtime error type) which is not guaranteed.Emitted objects examples:
