Closed hnph12 closed 2 years ago
@hnph12 Thanks for your comment. We will review the issue and get back to you shortly.
@hnph12 Thanks for bringing this up. I was also able to reproduce the same i.e., backend query for the chart is with filter AlertSeverity values "Error", "Critical", "Warning"... However, the AlertSeverity parameter of Alert kusto table is actually tagged with number 1, 2, 3, 4… instead of critical, warning, information... So the query is not returning any result no matter what.
Tagging @bwren to help confirm whether the solution is outdated or not & provide additional insights if any and enhance the document as appropriate.
Hi @hnph12, Thank you for your feedback. We passed the information on to the engineering team, but please keep in mind that this solution is based on old technology. It was only ever meant to report on the newer Azure Monitor alerts. It’s being replaced by newer functionality. Thanks, Abby
Hi All, when I deployed the alert management solution, I found that there will be no data in the summary dashboard even if I have couple of alerts triggered. After checked the backend query for the chart, I found it filter with AlertSeverity in ("Error", "Critical"). However, the AlertSeverity parameter is actually tagged with number 0, 1, 2, 3… instead of critical, warning, information… So the query will return no result no matter what.
Meanwhile, since this solution relies on query alert table, it cannot manage all the alerts. As the alert table only contains log alert and SCOM alerts. It doesn't contain metric alerts and activity log alerts.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.