I configured a Windows instance on AWS to start reporting logs and performance counters into their AWS Cloudwatch for centralised overview.

The day after I had started monitoring I found that it was consuming loads of CPU and memory and thus not normal,

Going into the instance, which took a while as it was so sluggish, I found that the EC2Config service was going berserk and I had to kill it.

Looking at the properties of the EC2 you can see that it was 2.2.12.30 and far from the version available today.

So if you want to enable Cloudwatch make sure that you first update the EC2config to be sure that your server will survive the burden of monitoring  ?

I have been doing some maintenance on a Hyper-V environment and patching with Windows updates and also firmware for the hardware.

The hosts was Dell R730 with former Broadcom and now Qlogic 10 Gbit NIC´s. There are 4 10 Gbit NIC´s on every host and they are set up with one team for management and one team for VM´s.

I have done firmware update before but now there was a new version that I wanted to apply.

It tock a while before I realised that the NIC`s had changed name and thus that was why the teams was degraded, we had some discussions and the Networking guy checked his configuration more than once and we also verified the cabling on the server and then after a while I realised that the NIC actually had changed name and once adding the correct NIC´s to the teams the status changed to normal!

So when doing maintenece please check the status after updating firmware or the battle with the networking guys can end in misery on your side 😉