-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
False
-
None
-
False
-
-
Issue Description:
Our v2 implementation lacks any support for "Error Handling".
We need to provide an implementation presumably comparable to that in v1.
Acceptance Criteria:
An agreement on what we mean by and can do to support Error Handling in v2.
Out of Scope:
The implementation!
Additional Information:
There is a clear demarcation between design-time errors (both pre-provisioning and during provisioning) and runtime errors (handling of events themselves).
Design Time errors
- Should produce an appropriate HTTP response from our User-facing APIs if the error occurs handling the User-request
- Should produce a FAILED resource with appropriate status message
Runtime errors
v1 attached to Managed Connectors DLQ and observed messages that were then enriched and copied to RHOSE's internal "Error Handling Topic" that Users could observe. v1 had an addon developed to monitor the topic and write messages to a database where from Users could poll and retrieve a log of errors.
- is related to
-
MGDOBR-1350 Investigate and propose Sink API for v2
- Closed