NeophyteNeophyteHi Mike,
1. Even after 12 hours the alert on Win_WMI_Access_Denied_ErrorCodes check on port 135 is not cleared after it started working.
2. Using Wbemtest from collectors to make sure wmi can be accessible from the collector.
3. Also using the debug console with explicitly mentioning the wmi username and password can get the metrics but if I run the debug command without mentioning creds it gives access denied error.
4. After that I'm clicking on refresh properties button as mentioned in the screenshot.
5. If I reload the device page all the missing datasources are applied, Alert is cleared, metrics started to poll.
ProfessorHmm, I didn't even realize there was a "Refresh Properties" option, never used it before :) I generally use AutoDiscover to force update when I'm in a hurry. Sound like it would be equivant in this case.
Might need to ask support but my guess is that LM does it first discovery, fails to detect anything and you may need to wait 24+ hours for it to run again, without forcing it manually. As a workaround I would suggest attempting to delay having LM detect the new EC2 instance until it's fully ready for monitoring. For example you can setup a Tag in EC2 that is something like monitoring=true only after your configurations are complete, and setup LM to only auto-add those devices that have that tag set.
