Collection

If you are trying to add a VMWare server and are getting a time out error please be sure that the SNMP service is running on the VMWare machine by doing the following.

A more efficient ping was introduced for version 6.2. If you do not wish to upgrade these are the steps to implement it.

1. Grab the patch (Right Click Save Target As)
2. You will need to stop your Longitude Services from Services.msc
3. Place the files in the patch into the following directories Longitude\common\lib\firenze-common.jar
   Longitude\dc\lib\firenze-collectors.jar
4. Start the services back up
5. The ping fix is now implemented

In order to change the Disk Task Interval you will have to do the following

1. Stop all of your services from services.msc
2. Navigate to Longitude\Applications\Windows\Collections.
3. Open up the file Windows_Disk.xml in Wordpad or Notepad.
4. You will need to edit the file to the schedule you want.. You can choose from EveryFifteen, EveryTwenty, EveryHalfHour, and EveryHour. Change the Italics to the schedule you would like modifying the interval to the number of seconds... (e.g. 3600 seconds per hour)
5. ConsolidatorCollections Count="1"
   

After registering a Windows application, Disk and/or Disk I/O collections may not be available. The Windows application has 2 different methods for collecting Disk data, and 3 different methods for collecting Disk I/O data. When a Windows application is registered, Longitude will make a best guess as to which version of collector to use, but may need to use an alternate collector if the initial collector fails. After several consecutive collection failures, the Disk or Disk I/O collection method will failover to an alternate method.

Longitude automatically introduces a skew factor of up to 10% of the interval in order to spread the load of data collection. However, users can introduce a specific offset by using the skew parameter in the schedule XML file for a Longitude collector.

Longitude schedule files are located under Longitude\applications\Application Name\collections, with each collector in the application having an associated application_collector.xml file. For example, the Windows CPU collection has a collection file:

If a collection can return multiple entities (for example, services or processes), you can add filter parameters in order to exclude some entities from being collected. To add filter parameters:

1. On the Manage Monitoring screen, click on the application icon for the application that includes the collection.
2. From the Application Monitoring Details page, click the Modify button next to the collection that you want to modify.

If a collection is failing, but you don't care about the collection and don't want it to affect the color of the computer's application icon on the Manage Monitoring page, you can disable the collection. If the collection is marked as optional in the collection list of the application, you can disable it as follows:

1. In Manage Monitoring, click on the application icon for the computer
2. Click the Modify button for the collection that you want to disable
3. Uncheck the Enabled box