心跳表与DeviceHeartbeat表 [英] Heartbeat table vs DeviceHeartbeat table

问题描述

大家好

我配置的警报在过去24小时内遇到无响应的集线器时遇到一些问题.此警报在查询下运行，但我发现心跳表最近没有数据.我修改了查询并将其更新为查询DeviceHeartbeat 表，这似乎按预期方式工作.我的问题是，您是否知道心跳表是否已过时并被DeviceHeartbeat取代，或者LogAnalytics中是否有任何重大更新?我最近在使用其他脚本时也遇到了类似的问题.

查询

Hi Everybody

I´m experiencing some issues with the alert I configured to get unresponsive hubs in the last 24hs. This alert runs below query but I found that there is no data coming from the Heartbeat table lately. I modifed the query and updated it to query the DeviceHeartbeat table and this seems to be working as expected. My question is, do you know if the Heartbeat table was deprecated and replaced by DeviceHeartbeat or if there was any major updated in LogAnalytics?. I´ve been experiencing similar issues lately with other scripts.

Query

心跳| 总结 LastCall = max(TimeGenerated) 由 其中 LastCall< ago( 12 h)

Heartbeat | summarize LastCall = max(TimeGenerated) by Computer | where LastCall < ago(12h)

推荐答案

Mveron，很高兴您能够通过DeviceHeartbeat表使用它.我不知道Log Analytics或Device Heartbeat的任何重大更新都可以替代Heartbeat表.您上面的陈述似乎支持您的假设.我是 在内部工作以获得权威的答案.直到那时，请继续使用您的查询来定位设备心跳"表.

Hi Mveron, glad you were able to get this working with the DeviceHeartbeat table. I am not aware of any major updates to Log Analytics or Device Heartbeat being a replacement to Heartbeat table. Your statement above seems to support your hypothesis. I am working internally to get an authoritative answer. Till then, please continue to target Device Heartbeat table with your queries.

干杯.

这篇关于心跳表与DeviceHeartbeat表的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！