Azure 事件网格重试失败
Azure Event Grid failed retries
Documentation on retries 指出，在预定义的 2 小时重试期（服务 GA 时为 24 小时）后，重试被抓住。未成功交付的事件会怎样？有没有一种方法可以使用 Storage blob 之类的东西来存储它们？
我是 Azure 事件网格团队的 Microsoft 项目经理。文档是正确的，而在预览版中，该服务将丢弃 2 小时内未送达的消息。当我们使这项服务普遍可用时（输入时尚未确定日期）或什至在此之前，我们会将此时间增加到 24 小时。在我们普遍提供此服务之前，我们正在认真考虑您在 Blob 存储中存储消息的想法。
Azure EventGrid 后的更新现已正式发布：
来自文档 (Event Grid message delivery and retry)：
Event Grid uses an exponential backoff retry policy for event delivery.
Event Grid adds a small randomization to all retry steps. After one hour, event delivery is retried once an hour.
By default, Event Grid expires all events that aren't delivered within 24 hours. You can customize the retry policy when creating an event subscription. You provide the maximum number of delivery attempts (default is 30) and the event time-to-live (default is 1440 minutes).
When Event Grid can't deliver an event, it can send the undelivered event to a storage account. This process is known as dead-lettering. By default, Event Grid doesn't turn on dead-lettering. To enable it, you must specify a storage account to hold undelivered events when creating the event subscription. You pull events from this storage account to resolve deliveries.
有关设置死信位置的示例，请参阅 Dead letter and retry policies。
Documentation on retries 指出，在预定义的 2 小时重试期（服务 GA 时为 24 小时）后，重试被抓住。未成功交付的事件会怎样？有没有一种方法可以使用 Storage blob 之类的东西来存储它们？
我是 Azure 事件网格团队的 Microsoft 项目经理。文档是正确的，而在预览版中，该服务将丢弃 2 小时内未送达的消息。当我们使这项服务普遍可用时（输入时尚未确定日期）或什至在此之前，我们会将此时间增加到 24 小时。在我们普遍提供此服务之前，我们正在认真考虑您在 Blob 存储中存储消息的想法。
Azure EventGrid 后的更新现已正式发布：
来自文档 (Event Grid message delivery and retry)：
Event Grid uses an exponential backoff retry policy for event delivery.
Event Grid adds a small randomization to all retry steps. After one hour, event delivery is retried once an hour.
By default, Event Grid expires all events that aren't delivered within 24 hours. You can customize the retry policy when creating an event subscription. You provide the maximum number of delivery attempts (default is 30) and the event time-to-live (default is 1440 minutes).
When Event Grid can't deliver an event, it can send the undelivered event to a storage account. This process is known as dead-lettering. By default, Event Grid doesn't turn on dead-lettering. To enable it, you must specify a storage account to hold undelivered events when creating the event subscription. You pull events from this storage account to resolve deliveries.
有关设置死信位置的示例，请参阅 Dead letter and retry policies。