...
| Page Properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Objective
Success metrics
...
Goal
...
Metric
Assumptions
Milestones
...
Provide a standardized way for errors to be returned from REST requests made to OpenMethods service endpoints.
Requirements
Requirement | User Story | Importance | Jira Issue | Notes | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Follow REST best practices for errors |
| |||||||||
| 2 | Ability to differentiate between system level errors and application errors |
|
|
|
|
|
...
| 3 | Support for compound errors | ||||
| 4 | Error content should be context survivable | The error content should contain enough information about the context in which it happened so it can be logged and understood later |
User interaction and design
Example Error Content
| Code Block | ||
|---|---|---|
| ||
{
"requestURL": "<full url that produced the error>",
"requestMethod": "<GET | POST | PUT | PATCH | DELETE | OPTIONS>",
"requestBody": "<any post/put/patch content of the request>", //optional
"httpStatus": "<http response code>",
"errorCode": "<error code>", //optional
"errorMessage": "<human readable error message>",
"errorRawMessage": "<original third-party error message>", //optional
"stackTrace": "<encoded text blob containing language specific stack trace information>", //optional
"causedBy": //optional
{
<full content of error>
}
} |
Open Questions
Question | Answer | Date Answered |
|---|---|---|
...