1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
You can add a CloudWatch logs target to a rule that catches all the events. You will then be able to see the events in CloudWatch Logs.
Not sure what you mean with the get back Ack/Nack. Get from where?
You can add a CloudWatch logs target to a rule that catches all the events. You will then be able to see the events in CloudWatch Logs.
Not sure what you mean with the get back Ack/Nack. Get from where?
Not cloudwatch logs , some other source or where the events are stored or queued within event bridge. Ack / back from event bridge saying it has received the event / msg - one way is that when we putevent we get if its success or failure
You do not have visibility into the internal works of EventBridge. You have some metrics that tell you what happened.
You always get an ACK (200 OK) when EventBridge receives the message, otherwise you should retry sending it. The PutEvent API is synchronous. If it return 200 OK, it means the message was received.
so basically we configure below archive DLQ metric on event bridge logs of the put event from code and create our own visualization so that we have a detailed picture