如何监控并报告异步调用并发 lambda 的失败？
我有这个lambda，其中首先调用自己30-40次以同时处理数据。使用异步火灾发生调用，忘记事件调用类型。一个实例显然在调用完成后死亡。
我希望第一个lambda在调用后活着，并报告触发的实例数，以及是否有lambdas通过SNS通知失败。因此，我切换到requestResponse Invocation类型，但是这里的问题现在是我的lambda调用一个实例等待实例的响应（可以花费几分钟），然后调用下一个。
我该如何异步调用Lambdas，但仍会从一开始就获得报告和跟踪？
I have this lambda in which the first instance invokes itself 30-40 times to process data concurrently. Invocation happens using the async fire and forget Event invocation type. The very first instance obviously dies after invocation completes.
I want the first lambda to stay alive after invocation and report on number of instances triggered and if any lambdas failed through SNS notifications. So I switched to RequestResponse invocation type, but the problem here is now my lambda invokes one instance waits for the response from the instance (which can take minutes) then invokes the next one.
How can I invoke lambdas asynchronously but still get the reporting and tracking from the first instance?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您可以报告使用第一次 Lambda 调用触发的实例数。
对于故障，不可能使用相同的 Lambda 实例，因为错误可能会发生在更远的地方（正如您提到的，可能需要几分钟才能完成）。但是，您可以配置并行运行的实例以报告调用状态。
事实上，有一个内置功能可以实现这一点。请参阅此链接。也就是说，您可以将调用记录（请求和响应信息）发送到SQS。通过使用队列，您应该能够获得成功和失败实例的报告。
You can report on the number of instances triggered using the first Lambda invocation.
For failures, it is not possible to use the same Lambda instance, as the error may happen much further down the line (as you mentioned, it may take minutes to complete). However, you can configure the parallelly running instances to report on the invocation status.
In fact, there is a built-in feature for this. Refer to this link. That is, you can send the invocation records (request and response information) to SQS. By consuming the queue, you should be able to get a report of success and failed instances.