VMware

Supported Versions ESX Server 4.0, 4.1; ESXi Server 4.0, 4.1, 5.0, 5.1, 5.5, 6.0,6.5; vCenter 4.0, 4.1, 5.0, 5.1, 5.5
Collection Methods VMware API
Requirements Username and Password for an account that can connect to a vCenter server and view VMware configuration. An administrator account within VMware is preferred.
Configuration
  1. Use Monitor Devices.
  2. Select VMware.
  3. If necessary, select a Longitude Remote Agent.
  4. Enter the name of a vCenter server or VMware ESX Host in the Computers field.
  5. Enter a Username. If you are monitoring a vCenter server, enter Domain\Username
  6. Enter the Password for the Username.
  7. Enter the number of Sockets used by the hosts managed by the vCenter server, or the number of sockets on the VMware ESX host. This number should be the same as the number of sockets used to license VMware. If you are not sure of the number, enter as many as allowed by your license, and modify the property later.
  8. Click on the Monitor button.
Troubleshooting

 

WindowsEventLog

Supported Versions Windows XP, Vista, 7, 8, 2000, 2003, 2008, 2012, 2016
Collection Methods WMI
Requirements
  • The Longitude Statistics Server account must have Local Administrator privileges on the monitored computer.
  • The Windows Management Instrumentation (WMI) service must be running on the monitored computer.
  • Windows Event Log severities will translate to Longitude severities as follows:
    Window Event Log Longitude
    Error Critical
    Warning Warning
    Failure Audit Major
  • WindowsEventLog collections may be filtered by Event ID or Source. If a collection is configured to look for a specific event, modify the Instance to be a unique name so that it does not overwrite a previously registered collection. Each monitored computer can support multiple WindowsEventLog Instances, creating collectors for specific Event IDs, Sources, Event Types, and Event LogFiles.
Configuration
  1. Use Monitor Devices.
  2. If necessary, select a Longitude Remote Agent.
  3. Select WindowsEventLog
  4. Enter the name of the computer to be monitored in the Computers field.
  5. Select the LogFile to monitor. The options are Application, System, Security, and Other. If Other is selected, the field will allow you to enter a LogFile name. The Instance field will be updated to match the LogFile.
  6. Select the types of Windows Events to collect in the Type Allow List. The options are Error, Warning, and Failure Audit.
  7. Optionally, enter Event IDs into either the Event Allow List or the Event Deny List. Do not enter Event IDs into both lists.
  8. Optionally, enter Sources into either the Source Allow List or the Source Deny List. Do not enter Sources into both lists.
  9. The Instance value is used by Longitude to distinguish between different WindowsEventLog collections being monitored for the same computer. Registering the same WindowsEventLog Instance twice for the same computer will overwrite the details of the previous registration. The default value for the Instance will be the LogFile – the instance value may be edited before registration.
  10. Click Monitor
Troubleshooting WindowsEventLog collection timeout error:
If a very large number of Windows Event Log records have been created within the last 5 minutes, it is possible that the collector will timeout. Check the Event Logs on the computer being monitored for excessive Windows Events.

 

Windows

Supported Versions Windows XP, Vista, 7, 8, 2000, 2003, 2008, 2012, 2016
Collection Methods WMI
Requirements
  • The Longitude Statistics Server account must have Local Administrator privileges on the monitored computer.
  • The Windows Management Instrumentation (WMI) service must be running on the monitored computer.
Configuration
  1. Use Monitor Devices or see the Windows instructions for Device Discovery.
  2. If necessary, select a Longitude Remote Agent.
  3. If monitoring manually, select Windows
  4. Enter the name of the computer 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.