VOLUMES SHOW IN APPSTACK, BUT NOWHERE ELSE

iosman123

Hello,

I have about 1500 Hyper-V hosts already in monitoring. I originally added these with a network discovery, but left out the volumes (C:\ \ E:\) because at the time, we couldn't monitor them due to lack of APEs. Now that we have enough resources and priorities have changed, we would like to monitor these 3 volumes on each server.

I re-ran a discovery for the hosts, selected the volumes i wanted to monitor, and then imported. I noticed during the import i got this message for the volumes: Volume C:\ Label:OSDisk Serial Number XXXXXXXXX, Parent Node: XXXXXX, Import Status: not processed.

Now i can see the volumes in the AppStack (honestly they may have already been there, i just really never noticed), but they are not actually being monitored. i confirmed this by listing the resources for a few individual hosts and sure enough the volumes do not have a check in their box. Am i missing something? is there a better way to add these volumes into monitoring?

thanks,

iosman

serena

iosman123  wrote: Hello, I have about 1500 Hyper-V hosts already in monitoring. I originally added these with a network discovery, but left out the volumes (C:\ \ E:\) because at the time, we couldn't monitor them due to lack of APEs. Now that we have enough resources and priorities have changed, we would like to monitor these 3 volumes on each server. I re-ran a discovery for the hosts, selected the volumes i wanted to monitor, and then imported. I noticed during the import i got this message for the volumes: Volume C:\ Label:OSDisk Serial Number XXXXXXXXX, Parent Node: XXXXXX, Import Status: not processed. Now i can see the volumes in the AppStack (honestly they may have already been there, i just really never noticed), but they are not actually being monitored. i confirmed this by listing the resources for a few individual hosts and sure enough the volumes do not have a check in their box. Am i missing something? is there a better way to add these volumes into monitoring? thanks iosman

hello, a few more pieces of information could be helpful here - are you using the windows agent or agentless WMI polling to gather this information? Have you created a support ticket with us to allow us access to diagnostics?