MicrosoftHi,
We've been using this solution successfully since 2023, and it has been working flawlessly for monitoring our Windows DHCP servers through Azure Monitor, DCR, and Log Analytics.
However, we recently started experiencing issues after the Azure Monitor Agent (AMA) was upgraded to version 1.42. DHCP logs collected through Custom Text Logs stopped being ingested correctly into our Log Analytics Workspace. We observed a gradual decrease in the number of records collected until ingestion eventually stopped completely.
After working with Microsoft Support, we rolled back AMA to version 1.38 and the issue was immediately resolved. DHCP logs started flowing again and have remained stable since the downgrade.
Microsoft is currently investigating the issue with us, but I'm curious if anyone else using this DHCP monitoring solution has experienced similar problems with AMA version 1.42 or later, particularly with Custom Text Logs and DHCP log rotation.
Thanks!
Not exactly the same issue, but within a few days of upgrading to 1.42 we started having issues where the DHCP service was unable to write to its DB file, causing reconciliation issues between our two DHCP servers. Uninstalled AMA completely and that resolved the issue. Did you ever hear any more back from MS, or are you still running on 1.38 for now?
MicrosoftHello pat72 and Eric_Frandsen ,
unfortunately I never heard such things.
