You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log lines generated by uncaught errors, such as throw new Error("foobar");, do not have any identifiable attribute that allows to programatically check if the log line comes from an uncaught throwable.
Other cases include the "browser not found in registry" error:
time="2024-07-12T16:47:49+02:00" level=error msg="Uncaught (in promise) GoError: browser not found in registry. make sure to set browser type option in scenario definition in order to use the browser module\n\tat github.com/grafana/xk6-browser/browser.syncMapBrowser.func7 (native)\n\tat file:///tmp/roobre/browser.js:20:15(4)\n" executor=shared-iterations scenario=default
Observe the matching log line does not have any attribute.
Expected behaviour
A log attribute would be nice to identify this logs programmatically and react to them. Something like source=throwable or something along those lines.
Actual behaviour
As described above.
The text was updated successfully, but these errors were encountered:
roobre
changed the title
Log messages for uncaught exceptions do not have source (or any other identifiable attribute)
Log messages for uncaught errors do not have source (or any other identifiable attribute)
Jul 12, 2024
Brief summary
Log lines generated by uncaught errors, such as
throw new Error("foobar");
, do not have any identifiable attribute that allows to programatically check if the log line comes from an uncaught throwable.Simples reproduction would be something like:
Other cases include the "browser not found in registry" error:
k6 version
k6 v0.52.0 (commit/20f8febb5b, go1.22.4, linux/amd64)
OS
Arch linux
Docker version and image (if applicable)
No response
Steps to reproduce the problem
k6 run --log-format logfmt --log-output=file=throw.log
Observe the matching log line does not have any attribute.
Expected behaviour
A log attribute would be nice to identify this logs programmatically and react to them. Something like
source=throwable
or something along those lines.Actual behaviour
As described above.
The text was updated successfully, but these errors were encountered: