Chat now with support
Chat with Support

Foglight for Storage Management Shared 4.6 - User and Reference Guide

Getting Started Monitoring Storage Performance Investigating Storage Devices Investigating Storage Components Investigating VPLEX Storage Troubleshooting Storage Performance Managing Data Collection, Rules, and Alarms Understanding Metrics Online-Only Topics

Modifying Data Collection Schedules

Generally speaking, the default data collection schedules are suitable for most environments. If you notice that some agents take an extended time to collect topology data or performance data, and modifying your monitoring environment is not a suitable solution, you may want to change the data collection schedules for the affected agents. You can find the current duration of collections in the Edit Agent Properties dialog box.

Understanding Data Collection Types and Schedules

Storage Collector agents perform two types of collections: topology collections and performance collections.

Topology collections

During topology collections, Foglight for Storage Management gathers basic information regarding each object and its child objects. For example, on an array object, LUN, disk, and children information is gathered. Foglight for Storage Management gathers various attributes and parameters (for example, size or capacity) as well as relationship data. This relationship data is the key to understanding the basic topology and interconnects, or paths, between objects (parent to parent, child to parent and, where appropriate, child to child). Without this relationship information performance analysis would not be possible.

Performance collections

During performance collections, Foglight for Storage Management gathers the following basic types of information:

•
Performance metrics for each known object (an object is known if it has previously been collected during a topology collection).
•
The performance collection enumerates objects and their children. This enumeration determines if there is any change in the topology (for example, a LUN has been created, a new ESX server has been added to a cluster, or a new VM has been created). As the collector recognizes changes in the environment (sometimes in conjunction with the server) it schedules topology collections to ensure that Foglight for Storage Management continually has an accurate understanding of the underlying topology. Not all topology changes can be detected by the performance collection. A scheduled topology collection will pick up any undetected changes.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating