AppInsight与功能应用程序不关联InvocationId和OperationId [英] AppInsight with Function app not correlating the InvocationId and OperationId

问题描述

Hello Team，

Hello Team,

你能否确认Appinsight在OperationId的运行方式上是否有任何变化与Function App invocationId相关联。因为从4月11日左右开始我们肯定会看到一些行为上的变化。

Can you please confirm if there is any change in Appinsight in the way how the OperationId is correlated to the Function App invocationId. Because definitely we are seeing some change in the behavior since around 11th Apr onward.

基本上，我们有功能应用程序，在消费计划和一些自定义上运行3个功能使用TelemetryClient跟踪依赖关系。

Basically, we have Function app with 3 functions running on the consumption plan and some custom dependency traced using the TelemetryClient.

在4月11日之前，我们曾经看到每次调用函数时OperationId都不同，并且所有跟踪和自定义依赖关系都与彼此很好。见下文  Pic1 。

但是现在似乎改变了相关性的发生方式。请参阅  Pic2 。对于不同的InvocationId，为不同的
OperationName给出了相同的OperationId。我不确定我错过了什么。我还可以确认在此期间我们还没有发布任何内容。

However now something seems to be changed the way how the correlation happening. Please see the Pic2. Same OperationId given for the different OperationName for different InvocationId. I'm not sure what I'm missing. I can also confirm that we have not released anything into production during that time.

有人可以帮我理解这里发生了什么。

Could someone help me to understand what is happening here.

问候，

Ram

Ram

Pic1：4月11日之前

Pic2：

推荐答案

Github Repo 。你可以按照进度跟随那里。



感谢报道！

This issue is being tacked in Github Repo by engineering team. You can follow there with the progress.

Thanks for reporting!

这篇关于AppInsight与功能应用程序不关联InvocationId和OperationId的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！