Skip to content

Releases: durrante/AVDMonitoringBaseline

v2.4.0

Choose a tag to compare

@durrante durrante released this 06 Jul 12:23

Fixes

  • Host Pool Capacity alerts (50/85/95%) never fired. The KQL parsed the runbook's decimal load percentage with toint(), which silently returns null on a non-integer string like 68.5, so every threshold comparison failed regardless of actual host pool load. Switched to toreal().
  • Host Pool Capacity alerts had no linked resource. HPResourceId read the wrong pipe-delimited field index (13 instead of 12) in the runbook output.
  • Service Health alert typo fixed: Serivice Issue -> Service Issue.

Improvements

  • Available Memory, Local Disk Free Space, and Azure File Share alerts now surface the actual value that triggered them (AvailableMB, CounterValue, PercentAvailable) as alert dimensions, instead of computing it and discarding it.

Full details in CHANGES.md.

v2.3.0 - first maintained fork release

Choose a tag to compare

@durrante durrante released this 06 Jul 10:59

First release of the maintained AVD Monitoring Baseline fork. Includes upstream PR #839 (fixes deployment-blocking issue #812), KQL-based Available Memory alerts (fixes power-on false positives, issue #656), extended health-check mapping, FSLogix UserName/ProfilePath dimensions, re-tuned High CPU 85% alert, and a new CustomerName parameter for MSP multi-tenant attribution. Full details in patterns/avd/CHANGES.md and docs/Whats-New.md.