Repository navigation
Problem doing manual error reporting #64
Description
Hi, I have code that does:
// In a promise `then` handler:
myRegister(new Error('some error'));
// ...
// Elsewhere in the code:
errorHandler.report(theNewError);
but the stackdriver API response is:
{
"error": {
"code": 400,
"message": "ReportedErrorEvent.context must contain a location unless `message` contain an exception or stacktrace.",
"status": "INVALID_ARGUMENT"
}
}
The request that is sent to stackdriver is:
{
"serviceContext": {"service": "webApp", "version": "whatever"},
"context": {
"user": "Joe User",
"httpRequest": {
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36",
"url": "http://localhost:3000/"
}
},
"message": "Error: {\"type\":\"An error during API handling\"}\n at then(function (/Users/murphyke/Documents/code/myapp/web/src/actions.js:224:0)"
};
What is the recommendation? Do I have to annotate the error object somehow?
Unhandled exceptions are reported correctly.
Using Chrome, btw.
Activity
steren commentedon Jan 22, 2019
It seems that the
messageattribute is not recognized as being an exception by Stackdriver Error Reporting.Stackdriber Error Reporting expects stacktraces formatted as such
Would you mind providing an exact sample that reproduces the issue?
murphyke commentedon Jan 22, 2019
I am cranking for a deadline but will make a reminder to look at this ... hopefully next week.
bz2 commentedon Jun 11, 2019
I have reproduced this in our deployment, issue is not related to calling report directly, but comes from
stacktrace-gpsproducing invalid function names.Example response:
{ "error": { "code": 400, "message": "ReportedErrorEvent.context must contain a location unless `message` contain an exception or stacktrace.", "status": "INVALID_ARGUMENT" } }Example message from request:
The section of code from PruneCluster:
This would be correctly reported as
<anonymous>but has instead given'window.setTimeout(function'as the function name.Workarounds at the stackdriver-errors-js level are possible, if a bit awkward? Could use something like isVarName to strip out badly detection function names.
See also stacktracejs/stacktrace-gps#54 which is another problem with this part of the JS parsing.
ernsheong commentedon Jul 24, 2021
Seeing something similar in 0.8.0:
Payload:
Response: