Removing a custom health monitor produces 404 errors when the type is not specified

[joel74]

I added a custom health monitor. When I removed it using Remove-HealthMonitor - specifying the name but not the type, a bunch of 404s were thrown. It looked like it was searching through all the different kinds of monitors.

I found that if I specify the type along with the name, I get no 404s. One option is to not return 404s. Another option would be to require a value for the type param.