Skip to content
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

[Stitching] Better errors #827

Open
alloy opened this issue Nov 22, 2017 · 0 comments
Open

[Stitching] Better errors #827

alloy opened this issue Nov 22, 2017 · 0 comments

Comments

@alloy
Copy link
Contributor

alloy commented Nov 22, 2017

These changes will likely require that we change errors to be objects rather than just message strings, will have to look into whether or that’s actually supported according to the spec.

  • Services and MP should start using HTTP status codes to reflect the type of error
  • Services should generate UUIDs for errors and:
    • log locally the details associated with that error UUID
    • include that UUID in the error payload
    • include whether or not it is a public or private error message
  • MP should only report the error UUID in case of a private error message
  • MP should annotate the error object with the service that the error originated from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant