We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
HttpErrorResponse
StackdriverErrorHandler
These errors do not have a stack trace, so the payload sent to the clouderrorreporting api was:
{ "serviceContext": { "service": "my-service" }, "context": { "httpRequest": { "userAgent": "Mozilla/5.0 ...", "url": "http://localhost:3000/app/123" } }, "message": "Error extracting stack trace: Error: Cannot parse given Error object\n[object Object]\n (::)" }
The service then responded with:
400 - ReportedErrorEvent.context must contain a location unless message contain an exception or stacktrace.
message
Errors without a stack would be serialized in a way to maintain as much information as possible.
It is surprising to send "Error extracting stack trace" instead of a message representing the error trying to be reported.
One quick fix I tried to implement was to JSON.stringify errors before reporting, those were rejected by the service as "too long".
JSON.stringify
Overall, would love if the client would do everything possible to ensure the error gets reported.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As is
HttpErrorResponse
StackdriverErrorHandler
These errors do not have a stack trace, so the payload sent to the clouderrorreporting api was:
The service then responded with:
Expected
Errors without a stack would be serialized in a way to maintain as much information as possible.
It is surprising to send "Error extracting stack trace" instead of a message representing the error trying to be reported.
One quick fix I tried to implement was to
JSON.stringify
errors before reporting, those were rejected by the service as "too long".Overall, would love if the client would do everything possible to ensure the error gets reported.
The text was updated successfully, but these errors were encountered: