Application Discovery Setup for Windows (Versions 6.1+)

Document created by Anson McCook Expert on Jun 11, 2018Last modified by praveen.vaddepally on Sep 18, 2018
Version 4Show Document
  • View in full screen mode

This document covers how to setup Application Discovery for Windows guests. Starting in version 6.1.0, Turbonomic uses WinRM to collect guest-OS and application metrics. For versions prior to 6.1.0, please see: Application Discovery Setup for Windows (Versions 6.0.x and Older) 

 

Upon completion of this setup, Turbonomic will be able to see vMem and vCPU consumption for specific application processes running on the Windows guest. You can optionally configure app priority to allow Turbonomic to determine when certain low-priority applications should be suspended when resources become constrained.

 

The high-level steps are:

  1. Add your application signatures to Turbonomic
  2. Configure WinRM on Windows guests
  3. Create a VM group in Turbonomic
  4. Target Windows VMs for Application Discovery

 

 

Add Your Application Signatures to Turbonomic

1) SSH into Turbonomic (default creds are root/vmturbo)

 

2) Change directory to:

cd /srv/tomcat/data/config/

 

3) Create a custom wmi-appSignatures file by copying the default:

cp wmi-appSignatures-default.xml wmi-appSignatures-custom.xml

 

4) Open the file and append new application signatures entries.

vi wmi-appSignatures-custom.xml

 

For example, to monitor the Google Chrome process running on a Windows guest, Turbo can match chrome.exe or generally chrome.*  to match any process containing the word chrome.

In my example, I added a new entry by following the existing formatting of the XML file:

 

<ApplicationSignature>

    <enabled>true</enabled>

    <name>Chrome</name>

    <match>chrome.*</match>

    <noMatch />

</ApplicationSignature>

 

Once you've added your entries, save the file:

:wq!

 

5) Now make your wmi-appSignatures-custom.xml file the main configuration to load:

vi sdk.probe.properties

Search for probe.WMI.appSignaturePath:

/probe.WMI.appSignaturePath

Remove the # and change the path to your wmi-appSignatures-custom.xml file we created in step 3.

Before:

# probe.WMI.appSignaturePath=config/wmi-appSignatures-default.xml

After:

probe.WMI.appSignaturePath=config/wmi-appSignatures-custom.xml

Save the file:

:wq!

 

 

Configure WinRM on Windows Guests

For the latest instructions, see the Enabling WMI section in the most recent Target Configuration Guide here: Turbonomic Documentation 

 

At the time of writing, the following steps will enable WinRM on most Windows guests:

1) Open Powershell with administrator access and run the following commands:

winrm quickconfig

winrm set winrm/config/service/auth '@{Negotiate="true"}'

winrm set winrm/config/service '@{AllowUnencrypted="true"}'

winrm set winrm/config/client '@{AllowUnencrypted="true"}'

 

 

2) Restart the Remote Registry service

 

 

Create a VM group in Turbonomic

1) In the new HTML5 UI, go to Settings > Groups

2) In the top right corner, select Create New Group > Virtual Machines

3) Create either a manual group or dynamic group that contains the Windows guests you would like monitor (and have WinRM enabled)

4) Save the Group

 

 

Target Windows VMs for Application Discovery

1) In the new HTML5 UI, go to Settings > Target Configuration

2) In the top right corner, select Add Target > Guest OS Processes > WMI

3) Fill out the following mandatory fields: 

Target Name = Any name that best describes this target

Username/Password =  Windows credentials

Scope = Select the group you made in the previous step

 

Note:

When local credentials are provided to Turbonomic, NTLM is the authentication mechanism. When domain credentials are provided, either NTLM or Kerberos can be specified. NOTE: If Kerberos is specified, the IP address of the target must be resolvable to a host name using DNS.

4) Click Add

 

 

 

Within a few minutes you should see new Application entries visible when you navigate to one of the targeted VMs.

 

4 people found this helpful

Attachments

    Outcomes