Discovery Pattern WMI Query times out

Eduard T
Tera Contributor

‎07-28-2022 01:27 AM

Hi all,

I am having a problem on the discovery of some attributes of Windows Servers (e.g cpu_count). There are times when a windows server is correctly discovered and the cpu_count is 4 for example, and times when the same windows server is discovered from the same mid server with the same credentials and the cpu_count will be set as empty.

Why is it set on empty? Because the WMI query in charge of retrieving this data sometimes fails (see attached screenshot).

How could I make this work?

Will increasing the mid.windows.probe_timeout property work?

Thank you in advance!

Labels:
Preview file
125 KB
0 Helpfuls
  • 1,116 Views
2 REPLIES 2

palanikumar
Giga Sage

‎07-28-2022 07:46 AM

This property is for a specify MID server. If you want to increase the timeout of all wmi calls then use wmi_timeout property

Thank you,

Palani

Thank you,
Palani
0 Helpfuls

Eduard T
Tera Contributor
In response to palanikumar

‎08-01-2022 11:40 PM

Hi @palanikumar ,

Thanks for your response. Is this "mid.sa.wmi.timeout" the property you are referring to? If yes, do you know whether this will solve the issue stated in the question? Thank you in advance!

0 Helpfuls