英文:
Azure Blob Storage PUT request returns no Result Code
问题
在应用洞察的“故障”中，我有一些依赖失败的状态码显示为“undefined”或“unknown”。
当我点击它们时，我发现事件链始于一个API调用。它向Azure Blob存储发送PUT请求。一个请求显示为“调用状态为false”，没有结果代码，紧接着总是有另一个请求显示为“调用状态为true”，并且“结果代码为201”，而其他依赖属性的所有行都是相同的。
我不明白“没有状态码”的故障是什么意思，也不知道如何处理它们。
有什么想法吗？
英文:
In Application Insights "Failures" I have dependency failures that have "undefined" or "unknown" status codes.
When I click on them I see that event chain begins by an API call. It makes PUT requests to Azure blob storage. One request has "Call status false" and no result code, always followed by another request that has "Call status true" and "Result code 201" while all other lines of dependency properties are identical.
I don't understand what the "no status code" failures mean or how to deal with them.
Any ideas?
答案1
得分: 1
当你看到一个"undefined"或"unknown"的状态码时，这意味着Application Insights无法捕获或接收到特定的HTTP状态码。
在你的情况下，似乎存在一个短暂的故障，这个故障会被一些重试逻辑处理。一些SDK或客户端内置了重试逻辑。如果由于网络中断、超时等短暂问题导致对Azure Blob Storage的初始请求失败，SDK可能会自动重试该请求。第一个失败的请求被记录为"Call status false"，然后立即重试成功，并返回一个"Result code 201"。
英文:
When you see an "undefined" or "unknown" status code, it means that Application Insights couldn't capture or didn't receive a specific HTTP status code from the dependency.
it seems that in your case there is a transient failure, which is handled by some retry logic. Some SDKs or clients have built-in retry logic. If an initial request to Azure Blob Storage fails due to transient issues like network blips, timeouts, etc., the SDK might automatically retry the request. The first failed request gets logged as "Call status false" and then the immediate retry is successful with a "Result code 201".
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论