[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Keith Zantow commented on JENKINS-39126 Re: Collect browser logs and publish via support-core A few notes Ivan, Cliff, and I had about this, from the UI perspective: Collect logs in memory, potentially using some amount of local storage Flush periodically in a background thread We need an easy JS utility API to offer channels and levels of logging If an error happens we might report more logs back to provide more context Things like SSE/connectivity errors, check the logs if there is a pending SSE error already and don't re-report the error Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39126 Collect browser logs and publish via support-core Change By: Michael Neale To enable better tracing of errors in blueocean, client side web console errors need to be collected and reported, via the server, to the support core plugin.In scope: * Trap all js errors on the client side* Publish errors to server side endpoint (jenkins under /blue/rest)* Server endpoint /errors to collect all error messages* A support core "Component" to publish client side logs/data to their own file as needed (similar to browser.md now)* Capture additional information (like headers/response payloads) for failures and publish them to server side endpointNice to have scope: * Client side component may not need be blueocean generic - if possible make it work with classic* Server side collection point may best live outside of blueocean if possible* support-core component may actually be able to be contributed to the support core plugin itself, meaning that there is no blueocean specific code in all this The support core plugin to report on things: https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin *Background and research so far* Some interesting reading: http://openmymind.net/2012/4/4/You-Really-Should-Log-Client-Side-Error/On reading what is out there for this, it really is quite simple. window.onerror now contains santised stacktraces as well as the error (if they help) so there is no real need for libraries. Many pay for services out there (rollbar is used for the dogfood instance, as an example) but this is probably best done without libs. onerror now has stacktraces: http://stackoverflow.com/questions/17687410/when-will-proper-stack-traces-be-provided-on-window-onerror-function Add Comment
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39126 Collect browser logs and publish via support-core Change By: Michael Neale To enable better tracing of errors in blueocean, client side web console errors need to be collected and reported, via the server, to the support core plugin.In scope: * Trap all js errors on the client side* Publish errors to server side endpoint (jenkins under /blue/rest)* Server endpoint /errors to collect all error messages* A support core "Component" to publish client side logs/data to their own file as needed (similar to browser.md now)* Capture additional information (like headers/response payloads) for failures and publish them to server side endpointNice to have scope: * Client side component may not need be blueocean generic - if possible make it work with classic* Server side collection point may best live outside of blueocean if possible* support-core component may actually be able to be contributed to the support core plugin itself, meaning that there is no blueocean specific code in all thishttps://wiki.jenkins-ci.org/display/JENKINS/Support+Core+PluginSome interesting reading: http:// jsnlog openmymind . com net / https 2012/4/4/You-Really-Should-Log-Client-Side-Error/On reading what is out there for this, it really is quite simple. window.onerror now contains santised stacktraces as well as the error (if they help) so there is no real need for libraries. Many pay for services out there (rollbar is used for the dogfood instance, as an example) but this is probably best done without libs. onerror now has stacktraces : http: // scotch stackoverflow . io com / tutorials questions / how 17687410/when - to will - log proper - client stack - side traces - _javascript_ be - errors provided-on-window-onerror-function Add Comment
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale edited a comment on JENKINS-39126 Re: Collect browser logs and publish via support-core NOTE: split this into server/client components if it makes sense for implementation There may be different errors we want to trap depending on the context: eg general unhandled errors, but also error reponses returned to fetch could be treated differently Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39126 Collect browser logs and publish via support-core Change By: Michael Neale To enable better tracing of errors in blueocean, client side web console errors need to be collected and reported, via the server, to the support core plugin.In scope: * Trap all js errors on the client side* Publish errors to server side endpoint (jenkins under /blue/rest)* A support core "Component" to publish client side logs/data to their own file as needed (similar to browser.md now)* Capture additional information (like headers/response payloads) for failures and publish them to server side endpointNice to have scope: * Client side component may not need be blueocean generic - if possible make it work with classic* Server side collection point may best live outside of blueocean if possible* support-core component may actually be able to be contributed to the support core plugin itself, meaning that there is no blueocean specific code in all thishttps://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin Some interesting reading: http://jsnlog.com/ https://scotch.io/tutorials/how-to-log-client-side-_javascript_-errors Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale commented on JENKINS-39126 Re: Collect browser logs and publish via support-core NOTE: split this into server/client components if it makes sense for implementation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39126 Collect browser logs and publish via support-core Change By: Michael Neale To enable better tracing of errors in blueocean, collection of logs from the client side if required web console errors need to be collected and reported, via the server, to the support core plugin .For In scope: * Trap all js errors on the client side * Publish errors to work, a server side component is required to collect the logs endpoint ( so the client side js can publish them jenkins under /blue/rest ) . The * A support - core plugin can be extended by implementing a "Component" extension point. This can then be used to write out the publish client side logs /data to their own file ( as an alternative needed (similar to inserting browser.md now)* Capture additional information (like headers/response payloads) for failures and publish them in the normal serverside log to server side endpointNice to have scope: * Client side component may not need be blueocean generic - which is if possible , but preferable to keep them separate) make it work with classic * Server side collection point may best live outside of blueocean if possible Support * support- core component may actually be able to be contributed to the support core plugin : itself, meaning that there is no blueocean specific code in all this https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin (this should be an optional dependency only) Add Comment
[JIRA] (JENKINS-39126) Collect browser logs and publish via support-core
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39126 Collect browser logs and publish via support-core Change By: Michael Neale Summary: Endpoint to collect Collect browser logs and publish via support - core component to publish them Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
