Applications List

Applications

The following is a list of applications monitored by Longitude – please click on the application name for specific configuration details:

Configuring properties for an application and submitting those properties with the Monitor button will trigger a test collection to verify that the configuration information is valid. If the test is successful, the configuration information will be written to the Longitude database and configuration files on the Longitude server selected to collect the data. This process is referred to as registering a collection.

Note that Longitude server refers to the Longitude Management Console or Remote Agent that has been selected to collect data for the application. The first application registered for a computer will assign the Longitude server for the monitored computer. Any applications monitored later will use the assigned Longitude server, regardless of the agent selected during configuration.

See Licensing for details on how license are units assigned for each monitored application.

Active Directory

Supported Versions Active Directory for Windows 2000, 2003 and 2008
Collection Methods WMI
Data Collected Active Directory Data CollectionsDownload PDF
Requirements
  • The Longitude Statistics Server account must have Local Administrator privileges on the ActiveDirectory server.
  • The Windows Management Instrumentation (WMI) service must be running on the Active Directory Server.
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select ActiveDirectory
  4. Enter the name of the Active Directory Domain controller to be monitored in the Computers field.
  5. Click Monitor
Troubleshooting
  • Collections fail with a No valid Counters error:
    The performance counters collected by this application have been corrupted or are not present. Rebooting the target computer may resolve the problem, or the counters may need to be manually reloaded. See the Microsoft website for more details about missing performance counters.
  • Collections fail to register with an Invalid Class error:
    The performance counters collected by this application are present on the system, but WMI cannot access them. To resolve the issue:

    1. Log on to the target computer with a local administrator account.
    2. Open a command prompt and run the command: winmgmt /resyncperf.
    3. Restart the Windows Management Instrumentation service on the target computer.

    Note: for Windows 2000 or Windows XP, the command in step 2 is: winmgmt /resyncperf Winmgmt_Process_ID where Winmgmt_Process_ID is the Process ID for the winmgmt process.

 

DHCP

Supported Versions DHCP Server for Windows 2000, 2003, 2008, 2016
Collection
Methods
SNMP and WMI
Data Collected DHCP Data CollectionsDownload PDF
Requirements
  • The SNMP Component for Windows DHCP has been installed on the DHCP server.
  • The SNMP, DHCP Server and Windows Management Instrumentation (WMI) services must be running on the DHCP Server.
  • The SNMP Service on the DHCP Server should be configured to allow Longitude to request SNMP data.
  • The Longitude Statistics Server account must have Local Administrator privileges on the DHCP server.
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select DHCP
  4. Enter the name of the DHCP Server to be monitored in the Computers field.
  5. Enter an SNMP V1 Community string with at least Read Only privileges in the Community field.
  6. UDP port 161 is the default SNMP request port. If SNMP on the DHCP server uses a different port, adjust the Portvalue.
  7. Leave the TimeoutSeconds value at 5 and the Retries value at 1. If the collection done at registration times out due to a slow connection, adjust these values and try registering again.
  8. Click Monitor
Troubleshooting
  • Collections fail with the message Error Registering DHCP Status…no statistic rows were returned:
    Longitude was able to contact SNMP, but the requested DHCP data was not returned. Verify that the SNMP component for Windows DHCP has been installed.
  • Collections fail with the message Error Registering DHCP Status…time out after retries:
    Longitude was not able to contact SNMP on the DHCP Server. Verify the following:

    • The SNMP Service is running on the DHCP Server.
    • The Longitude server has permission to request data via SNMP – this is configured on the Security tab of the SNMP Service Properties.
    • The SNMP Community string is correct.
    • The SNMP port is configured correctly, and there is nothing blocking traffic between Longitude and the DHCP server.
    • If the configuration is set up correctly, and there is a slow network connection between Longitude and the DHCP server, adjust the TimeoutSeconds and/or Retries properties to allow for slow or failed SNMP connections.

 

Exchange

Supported Versions Exchange 2016
Exchange 2013
Exchange 2010
Exchange 2007
Collection
Methods
WMI, PowerShell Exchange Management Shell scripts, File Parsing
Data Collected Exchange Data CollectionsDownload PDF
Requirements
  • The account assigned to the Statistics Server service must have the following properties:
    • Be a member of the Local Administrators group on the Exchange Servers from which statistics will be collected.
    • Be a domain account in the same domain as the Exchange server.
    • In order to collect Mailbox and Folder statistics the account must have “Read” access in Exchange.
  • The Exchange Management Shell (EMS) must be installed on the Longitude Agent used for Exchange collections. This tool can be installed by using the Exchange Installation CD and selecting only the Management Tools portion. The Longitude Statistics server will need to be running on a 64 bit OS to install the Exchange Management Tools.
  • The Exchange application will monitor a version specific default list of Exchange services. Any services on this list for the version of Exchange that you’re monitoring that have been installed but are not running will generate an alert. Additional services may be monitored using Service Transactions. The monitored services are:
    HostControllerService (Exchange 2016, Exchange 2013)
    IISAdmin (Exchange 2007)
    MSExchangeAB (Exchange 2010)
    MSExchangeADTopology (all versions)
    MSExchangeAntispamUpdate (Exchange 2016, Exchange 2013, Exchange 2010)
    MSExchangeDagMgmt (Exchange 2016, Exchange 2013)
    MSExchangeDelivery (Exchange 2016, Exchange 2013)
    MSExchangeDiagnostics (Exchange 2016, Exchange 2013)
    MSExchangeEdgeSync (all versions)
    MSExchangeFastSearch (Exchange 2016, Exchange 2013)
    MSExchangeFBA (Exchange 2010)
    MSExchangeFDS (Exchange 2010, Exchange 2007)
    MSExchangeFrontEndTransport (Exchange 2016, Exchange 2013)
    MSExchangeHM (Exchange 2016, Exchange 2013)
    MSExchangeIS (all versions)
    MSExchangeMailboxAssistants (all versions)
    MSExchangeMailboxReplication (Exchange 2016, Exchange 2013, Exchange 2010)
    MSExchangeMailSubmission (Exchange 2010, Exchange 2007)
    MSExchangeMigrationWorkFlow (Exchange 2016, Exchange 2013)
    MSExchangeProtectedHostService (Exchange 2010)
    MSExchangeRepl (all versions)
    MSExchangeRPC (Exchange 2016, Exchange 2013, Exchange 2010)
    MSExchangeSA (Exchange 2010, Exchange 2007)
    MSExchangeSearch (Exchange 2010, Exchange 2007)
    MSExchangeServiceHost (all versions)
    MSExchangeThrottling (Exchange 2016, Exchange 2013)
    MSExchangeTransport (all versions)
    MSExchangeTransportLogSearch (Exchange 2016, Exchange 2013)
    MSExchangeUM (Exchange 2016, Exchange 2013)
    MSExchangeUMCR (Exchange 2016, Exchange 2013)
    W3SVC (Exchange 2010, Exchange 2007)
  • The Windows Management Instrumentation (WMI) service must be running on the Exchange Server.
  • The optional TrackingLog collections require that Exchange Message Tracking be enabled. Please refer to Microsoft’s instructions for configuring message tracking.
  • A separate, dedicated Statistics Server is recommended to collect from an Exchange computer when the Exchange
    implementation is large (e.g. many hundreds of mailboxes or folders). Some of the nightly Exchange collections can
    take a long time for a large implementation, so dedicating a separate Statistics Server to those collections will
    allow them to be processed without holding up other non-Exchange collections.
Configuration
  1. Use Monitor Devices.
  2. If necessary, select a Longitude Remote Agent.
  3. Select Exchange2013, Exchange2010, or Exchange2007. If you are monitoring Exchange 2016, use the Exchange2013 application.
  4. Enter the name of the Exchange Server to be monitored in the Computers field.
  5. Enter the Roles to be monitored. The default is a * wildcard value for both roles, or you can select
    individual roles as needed from the following:

    • ClientAccess (or CA) (all versions)
    • Mailbox (or MB) (all versions)
    • Edge Transport (or ET) (Exchange 2010, Exchange 2007)
    • HubTransport (or HT) (Exchange 2010, Exchange 2007)
    • Unified Messaging (or UM) (Exchange 2010, Exchange 2007)

    If you are not certain which roles to monitor, use the default * wildcard value.

  6. The Servers value is the name used for scripted PowerShell collections. This is normally the same as the server name.
  7. Enter the Log Directory Path – this is the UNC path to the shared Tracking Log directory on the Exchange server. The default value for this is \\Exchange Server Name\MessageTracking. If message tracking is not enabled, this value may be left blank and can be configured later.
  8. Click Monitor
Troubleshooting
  • Collections fail with a No valid Counters error:
    The performance counters collected by this application have been corrupted or are not present. Rebooting the target computer may resolve the problem, or the counters may need to be manually reloaded. See the Microsoft website for more details about missing performance counters.
  • Collections fail to register with an Invalid Class error:
    The performance counters collected by this application are present on the system, but WMI cannot access them. To resolve the issue:

    1. Log on to the target computer with a local administrator account.
    2. Open a command prompt and run the command: winmgmt /resyncperf.
    3. Restart the Windows Management Instrumentation service on the target computer.
  • Exchange TrackingLog collection will fail to register if:
    • Exchange message tracking is not enabled. See Exchange Message Tracking Log Configuration.
    • The Exchange Server is monitored by its IP address rather than its name. If this is the case, remove the Longitude Exchange application for the IP address of the server and add it for the name of the server instead.
    • The Exchange Tracking Log folder is not shared.

 

Hyper-V

Supported Versions Hyper-V 2008, 2012, 2016
Collection
Methods
WMI
Data Collected Hyper-V Data CollectionsDownload PDF
Requirements
  • The Longitude Statistics Server account must have Local Administrator privileges on the Hyper-V server.
  • The Windows Management Instrumentation (WMI) service must be running on the Hyper-V Server.
Configuration
  1. Use Monitor Devices.
  2. Select Hyper-V.
  3. If necessary, select a Longitude Remote Agent.
  4. Enter the name of a Hyper-V server.
  5. Enter the number of Sockets used by the Hyper-V server.
  6. Click on the Monitor button.
Troubleshooting
  • Collections fail with a No valid Counters error:
    The performance counters collected by this application have been corrupted or are not present. Rebooting the target computer may resolve the problem, or the counters may need to be manually reloaded. See the Microsoft website for more details about missing performance counters.
  • Collections fail to register with an Invalid Class error:
    The performance counters collected by this application are present on the system, but WMI cannot access them. To resolve the issue:

    1. Log on to the target computer with a local administrator account.
    2. Open a command prompt and run the command: winmgmt /resyncperf.
    3. Restart the Windows Management Instrumentation service on the target computer.

 

IBM Director

Collection
Methods
SNMP
Data Collected IBM Director Data CollectionsDownload PDF
Requirements
  • The SNMP service must be running on the computer running IBM Director.
  • The SNMP Service on the IBM Director computer should be configured to allow Longitude to request SNMP data.
  • The IBMDirector application monitors the status of the following components:
    IBMDirector Component OID MIB
    Fan .1.3.6.1.4.1.2.6.159.1.1.80.3 IBM-SYSTEM-LMSENSOR-MIB
    Memory .1.3.6.1.4.1.2.6.159.1.1.120.1 IBM-SYSTEM-MEMORY-MIB
    Network .1.3.6.1.4.1.2.6.159.1.1.110.1 IBM-SYSTEM-NETWORK-MIB
    PowerSupply .1.3.6.1.4.1.2.6.159.1.1.130.1 IBM-SYSTEM-POWER-MIB
    Processor .1.3.6.1.4.1.2.6.159.1.1.140.1 IBM-SYSTEM-PROCESSOR-MIB
    Temperature .1.3.6.1.4.1.2.6.159.1.1.80.1 IBM-SYSTEM-LMSENSOR-MIB
    Voltage .1.3.6.1.4.1.2.6.159.1.1.80.2 IBM-SYSTEM-LMSENSOR-MIB
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select IBMDirector
  4. Enter the name of the IBM Director computer to be monitored in the Computers field.
  5. Enter an SNMP V1 Community string with at least Read Only privileges in the Community field.
  6. UDP port 161 is the default SNMP request port. If SNMP on the IBM Director computer uses a different port, adjust the Portvalue.
  7. Leave the TimeoutSeconds value at 5 and the Retries value at 1. If the collection done at registration times out due to a slow connection, adjust these values and try registering again.
  8. Click Monitor
Troubleshooting
  • IBMDirector registers successfully, but is not listed as a monitored application:
    All components in the IBMDirector application are optional, and no errors are logged if data is not returned. If there are no registration errors, but IBMDirector is not listed as monitored, verify:

    • IBMDirector is configured to respond to SNMP requests for the monitored OID values.
    • The SNMP Service is running on the computer running IBMDirector.
    • The Longitude server has permission to request data via SNMP – this is configured on the Security tab of the SNMP Service Properties.
    • The SNMP Community string is correct.
    • The SNMP port is configured correctly, and there is nothing blocking traffic between Longitude and the computer running IBMDirector.
    • If the configuration is set up correctly, and there is a slow network connection between Longitude and the computer running IBMDirector, adjust the TimeoutSeconds and/or Retries properties to allow for slow or failed SNMP connections.