From 5112146730efa9fa23a313af0d2229bced26d859 Mon Sep 17 00:00:00 2001 From: I867318 Date: Mon, 13 Sep 2021 13:06:18 -0600 Subject: [PATCH] Enhance DLQ CloudEvents with destination --- docs/developer/eventing/event-delivery.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/developer/eventing/event-delivery.md b/docs/developer/eventing/event-delivery.md index 4d071e75e0..e247131f9b 100644 --- a/docs/developer/eventing/event-delivery.md +++ b/docs/developer/eventing/event-delivery.md @@ -82,6 +82,17 @@ Failed events may, depending on the specific Channel implementation in use, be enhanced with extension attributes prior to forwarding to the`deadLetterSink`. These extension attributes are as follows: +- **knativeerrordest** + - **Type:** String + - **Description:** The original destination URL to which the failed event + was sent. This could be either a `delivery` or `reply` URL based on + which operation encountered the failed event. + - **Constraints:** Always present because every HTTP Request has a + destination URL. + - **Examples:** + - "http://myservice.mynamespace.svc.cluster.local:3000/mypath" + - ...any `deadLetterSink` URL... + - **knativeerrorcode** - **Type:** Int - **Description:** The HTTP Response **StatusCode** from the final event