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

Failed events are not enhanced with extension attributes #2340

Closed
egorlepa opened this issue Jun 16, 2022 · 8 comments · Fixed by #2374
Closed

Failed events are not enhanced with extension attributes #2340

egorlepa opened this issue Jun 16, 2022 · 8 comments · Fixed by #2374

Comments

@egorlepa
Copy link
Contributor

Describe the bug
Failed events are not enhanced with extension attributes prior to forwarding to the deadLetterSink as described here:
https://knative.dev/docs/eventing/event-delivery/#configuring-channel-event-delivery
(knativeerrordest, knativeerrorcode, knativeerrordata)

Expected behavior
I expect failed events to be enhanced with extension attributes.

Knative release version
1.5

Additional context
Sending event to deadLetterSink is kind of pointless without some context (where this event was meant to be delivered; what happened). There is not really much i can do with such event - i don't know which subscriber failed to consume it and why

@egorlepa egorlepa added the kind/bug Categorizes issue or PR as related to a bug. label Jun 16, 2022
@pierDipi
Copy link
Member

Hi @egorlepa, thanks for reporting!

I agree that we should add this feature to this implementation but I'm not entirely sure about the knativeerrordata, the body might be very large and it might not fit into a header.

I'll discuss this with the group (you're very welcome to join) because I don't think the data can be included in this way.

@pierDipi pierDipi added kind/feature-request and removed kind/bug Categorizes issue or PR as related to a bug. labels Jun 17, 2022
@egorlepa
Copy link
Contributor Author

hey, @pierDipi i believe default channel implementation can be used as a reference. it defines max body size as 1024 bytes, everything else gets truncated.
https://github.com/knative/eventing/blob/release-1.5/pkg/channel/attributes/knative_error.go

@egorlepa
Copy link
Contributor Author

Please, consider also adding information about sender (broker name/channel name/something like that). I am trying to create a single entry point for failed events and such information would help.

@pierDipi
Copy link
Member

pierDipi commented Jun 20, 2022

Hi @egorlepa, yes, I agree these are valuable attributes for debugging dead letter sinks, do you have the capacity to contribute this feature?

I'm available if you have any questions on the inner workings of the project and its components, or if you need guidance on the implementation.

@egorlepa
Copy link
Contributor Author

@pierDipi can't see why not, how may i contact you?

@pierDipi
Copy link
Member

you can reach out to us with these methods https://knative.dev/docs/community/contributing/#learn-and-connect or just with comments on this issue if you don't want to create accounts or join groups, etc.

We also run a meeting, Eventing Kafka WG, on Tuesday every other week, you can find it in this shared calendar https://calendar.google.com/calendar/u/0/embed?src=knative.team_9q83bg07qs5b9rrslp5jor4l6s@group.calendar.google.com&ctz=America/Los_Angeles

@matzew
Copy link
Contributor

matzew commented Jul 1, 2022

@egorlepa Are you interested in tackling this?

You can reach us on the resources that Pierangelo mentioned 😄

@egorlepa
Copy link
Contributor Author

egorlepa commented Jul 4, 2022

Yeah, sorry, last 2 weeks were very tough. I'll have time this week, also I joined slack

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants