DataSource Collection Attributes

Certain data collection methods require you to configure specific attributes in the Summary section of your DataSource.

Collection Method

The Collection Method reflects the name of the mechanism used to collect data for that DataSource. For example, use the OID object name for SNMP data or the WMI property name for WMI data. For more information, see Data Collection Methods.

Collection Schedules

The Collection Schedule defines how frequently data is collected. Select a collection schedule (polling cycle) that is appropriate for the type of data being collected. Metrics that change frequently (For example, CPU) or require immediate attention in the event of an error (For example, ping loss) should have a shorter polling cycle, such as one minute. Metrics that can tolerate a longer delay in alerting or change less frequently (For example, drive loss in a RAID system, or disk utilization) should have a longer polling cycle, such as five minutes.

Overriding Collection Schedule at the Resource or Resource Group Level

You can override the collection interval for a DataSource on a particular resource or for all resources in a resource group by assigning a numeric polling interval (in minutes) to the following custom property at the resource or resource group level:

[DataSourceName].pollinginterval

Ensure that you are using the DataSource name and not display name as both are present in the DataSource definition.

For more information, see Resource and Instance Properties. 

Multi-Instance

If there are multiple occurrences of an object in your DataSource that you want to monitor, then your DataSource is a Multi-Instance. For example, if you have multiple disks or volumes on a server that you are monitoring, toggle the Multi-Instance switch on. 

Using Wildvalue as the Unique Identifier

In case of multi-instance datasource, you can choose to use the wildvalue of an instance as its unique identifier by selecting Use Wildvalue as Unique Identifier.

• Selecting Use Wildvalue as Unique Identifier—The instance value (wildvalue) is used as the unique identifier and you can rename the instance without losing the instance history (instance data collected so far).
  If an instance with wildalias “test1” and wildvalue “1234” is renamed to “test2”, LogicMonitor still recognizes it as the same instance, so the data history from “test1” is preserved under “test2.”
• Not selecting Use Wildvalue as Unique Identifier—The instance name (wildalias) is used as the unique identifier. When you rename the instance (even if you do not change the instance value) LogicMonitor will consider it as a new instance. In this case, the history of the instance (before renaming) is not saved.
  If “test1” is renamed to “test2”, LogicMonitor considers “test2” as a new instance, and the history of “test1” is lost.

You can enable Use Wildvalue as Unique Identifier when setting up or editing a DataSource. However, once enabled, you cannot revert to using the wildalias as the unique identifier. The option remains disabled.

Selecting this option when building a DataSource, particularly when there is a UUID or another unique, persistent identifier, allows you to monitor name changes and instances with duplicate names.

In the case of scripted SNMP monitoring, where indexes might reorder (For example: “Ethernet 0” changing from index “1” to “3” after a reboot), using the wildalias as the unique identifier ensures that the instance remains consistent, even if the SNMP index changes.

Active Discovery

For more information, including configuration, see Active Discovery. 

Collection Arguments

For more information, see Data Collection Methods and Active Discovery. 

Datapoints

For more information, see Datapoint Overview.