Date: Thu, 28 Mar 2024 20:22:24 +0000 (UTC) Message-ID: <1650252897.69091.1711657344483@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69090_624674878.1711657344483" ------=_Part_69090_624674878.1711657344483 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
SQL Diagnostic Manager requires t= hat you enable either OLE automation or direct Windows Management Interface= (WMI) procedures for monitoring OS metrics. In addition, if your SQL Serve= r instance includes enabled Lightweight Pooling, SQL Diagnostic Manager can= not collect OS metrics information. If SQL Diagnostic Manager cannot provid= e OS metrics, a message displays on the Dashboard and Services Summary view= s providing more information.
When SQL Diagnostic Manager cannot collec= t OS Metrics due to the disabled collection, a bar displays a link to enabl= e OS metric collection procedures for your SQL Server version.
SQL Diagnostic Manager collects metrics that track the performance of th= e computers that host your monitored SQL Server instances. These metrics in= clude:
You can access the OS Metrics tab of= the Monitor SQL Server Properties window by right-clicking the approp= riate monitored SQL Server instance, and then selecting Properties. Click OS Metrics when SQL = Diagnostic Manager displays the Monitored SQL Server Properties window= .
OS metrics collection is not require= d in SQL Diagnostic Manager. However, if you disable this feature, SQL Diag= nostic Manager ceases to collect OS metrics and does not raise any pre= viously-associated alerts. You can easily re-enable OS metric collection at= any time if you decide that you want to continue collecting these metrics.=
It is preferred that the WMI user is a lo= cal administrator on the monitored SQL Server instance. However, if yo= u do not want to grant administrator access, use the following steps to con= figure remote WMI access in Microsoft Windows:
You also may need to add the WMI user account to the following policies:=
For more information about using a direct WMI connection, see the M= icrosoft document, Securing a Remote WMI Connection= .
Edit your specific registry settings to allow WMI to run out-of-pro= cess.
SQLdmoutofprocoleautomati=
on.reg
file onto each of your monitored SQL Server instances.=
li>
The following problems require user action before SQL Diagnostic Manager= can begin collecting OS metrics:
Select the Collect Operating System data using OLE Automation option to enable OLE Automation procedures.
The stored procedures= associated with OLE Automation are missing on the SQL Server instance= . SQL Diagnostic Manager cannot capture OS metrics until these stored proce= dures are available on the SQL Server instance.
The WMI Service on th= e monitored SQL Server instance may not be running. SQL Diagnostic Man= ager cannot collect OS metrics until this service is started.
This is an advanced f= eature used in symmetric multiprocessing environments in SQL Server. S= QL Diagnostic Manager cannot collect OS metrics until this option is disabl= ed on your monitored SQL Server instances.
SQL Diagnostic Manager all= ows you to configure the WMI timeout value. In some environments, customers= may experience WMI timeouts when their machine is too busy to respond in a= timely manner. Although WMI timeouts should not be ignored and often point= to an environmental issue, you can control this value when the behavior di= splayed is normal in your environment. The default WMI timeout value in SQL= Diagnostic Manager is of 90 seconds to reduce the number of intermittent e= rrors.
To configure the WMI timeout value:
SQLdmCollectionService.exe.=
code>Config
wmiQueryTimeOut=3D=E2=80=9D300=
=E2=80=9D
as a parameter to this node<Services>
<CollectionService instanceName=3D"Default" servicePort=3D"5167=
"
managementServiceAddress=3D"Server" managementServicePort=3D"5166"=
heartbeatIntervalSeconds=3D"180" wmiQueryTimeOut=3D"300"/>
</Services>