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.

Sign up for GitHub

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

Enhance DLQ CloudEvents with destination #4228

Merged
merged 1 commit into from
Sep 16, 2021
Merged

Enhance DLQ CloudEvents with destination #4228

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/developer/eventing/event-delivery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down