[英]Significance of trackedProperties_NAME_g and trackedProperties_NAME_s in Azure Logic-app trackedProperties?
Sometime we queries at one and get the value at another column, so thought of sharing this finding came across有时我们在一个列中查询并在另一列中获取值,因此想到分享这个发现
I have created a logic-app, with trackedProperties " MessageId " and attached with Log analytics workspace (Diagnostic settings).我创建了一个带有 trackedProperties“ MessageId ”的逻辑应用程序,并附加了日志分析工作区(诊断设置)。
How to add track properties to log analytics workspace in logi-app 如何将跟踪属性添加到 logi-app 中的日志分析工作区
"trackedProperties": {
"MessageId": "@{json(xml(triggerBody())).ABC.DEF.MessageID}"
}
When I queried in Log Analytics,there I saw 2 trackedProperties columns with the name trackedProperties_MessageId_g and trackedProperties_MessageId_s .当我在 Log Analytics 中查询时,我看到 2 个 trackedProperties 列,名称为trackedProperties_MessageId_g和trackedProperties_MessageId_s 。
Significance of above said 2 column names: When you provide a GUID value, it populates to trackedProperties_MessageId_g and when you provide string it populates to trackedProperties_MessageId_s .上述 2 列名称的意义:当您提供 GUID 值时,它会填充到trackedProperties_MessageId_g ,当您提供字符串时,它会填充到trackedProperties_MessageId_s 。
Thanks for sharing your finding(s).感谢您分享您的发现。 Yes, AFAIK when you send particular field/column to Log Analytics its name is changed based on the type.
是的,AFAIK 当您将特定字段/列发送到 Log Analytics 时,其名称会根据类型更改。 This is true for almost any field/column.
几乎所有字段/列都是如此。 However there are some fields/columns which are called reserved that you can send without name change if you send them in the right type of course.
但是,有些字段/列称为保留字段/列,如果您以正确的课程类型发送它们,则无需更改名称即可发送。 An MVP, Stanislav Zhelyazkov has covered this topic here .
作为 MVP,Stanislav Zhelyazkov 在这里讨论了这个话题。
If you are not expecting 2 trackedProperties with the names trackedProperties_MessageId_g and trackedProperties_MessageId_s and were expecting only 1 trackedProperty then I suggest you to share your feedback in this UserVoice / feedback forum.如果您不希望有 2 个名为 trackedProperties_MessageId_g 和 trackedProperties_MessageId_s 的 trackedProperty,并且只希望有 1 个 trackedProperty,那么我建议您在此UserVoice / 反馈论坛中分享您的反馈。 Responsible product / feature team would check feasibility on how this can be resolved by adding some kind of checkpoint in the background and then if it's really feasible to accomplish then responsible product / feature team would triage / start prioritizing the feedback based on various factors like number of votes a feedback receives, priority, pending backlog items, etc.
负责任的产品/功能团队将通过在后台添加某种检查点来检查如何解决此问题的可行性,然后如果确实可行,那么负责任的产品/功能团队将根据各种因素(如数量)对反馈进行分类/开始优先级排序反馈收到的票数、优先级、待处理的积压项目等。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.