Instance Monitoring State is Unknown

About a month ago I asked about why I had a much of health unknow (muted) on my instances. Turns out, that’s not the VM health but a group check.  So if I recreate a group and add the VM back in it… the health doesn’t update.  Should it?  Is it hardcoded to an ID that no longer exists and needs to manually be fixed?


I have started doing some stuff around this for a customer ticket today. Remind me to come back and update when I know more if I don’t within a week

So it takes updating monitor_check_group.instance_id with the instance ID when you create the new group.

That resolved the issue