Dell Vizioncore Manual de usuario descargar pdf (Pagina 372)

372 vFoglight

Administration and Configuration Guide

Observe the Manage Thresholds dashboard.

The newly-added threshold appears in the list.

Managing Retention Policies

Topology is a representation of—and a way of understanding—the logical and physical

relationship between items in your monitored environment. At run-time, vFoglight

dynamically builds topology models using the monitoring data about your system that is

collected by vFoglight agents. A model is a set of objects and relationships designed to

represent a monitored resource and its parts. vFoglight models retain collected data and

transform it into nodes, adding configuration data to each node as properties, and

attaching metric data to appropriate nodes as metrics. Topology models provide the

context for the metrics sent by the agents to the vFoglight Management Server.

Retention policies allow you to define time periods where monitoring data can be

sampled, aggregated, or purged from your system. All topology objects in vFoglight

form a hierarchy whose root is the super-type

TopologyObject. Retention policies are

inherited from the object’s type. These policies may be overwritten, in which case the

modification applies to all child types in the hierarchy.

In addition to retention policies, the collected data has additional life-cycle properties

that are defined in the

storage-config.xml file that is located in the directory

<vfoglight_home>/config. For example, according to the default retention policy for

TopologyObject, all data is rolled up to 15 minute periods after the age of 15 minutes,

then rolled up to one-hour periods after the age of four hours, and finally rolled up to

four-hour periods after the age of five days. Furthermore, the default settings in

storage-config.xml dictate that the 15-minute interval data is kept for three days

and is converted to one-hour interval data, while one-hour interval data is kept for two

weeks and then converted to four-hour interval data.

If there is no existing retention policy for a topology type, that type inherits the retention

policy from its parent type. If no policies exist within the entire hierarchy, the type

inherits the policy from the

TopologyObject type. Conversely, setting a retention

policy for a topology type completely overwrites any policy it inherits from a super-

type, and is applied to all sub-types of that topology type. For an example of how to

configure a retention policy in cases where data storage is limited, see “Example:

Addressing Data Storage Concerns” on page 390

You create new retention policies and manage the existing ones using the Manage

Retention Policies dashboard. For complete information, see the following sections:

1 2 ... 367 368 369 370 371 372 373 374 375 376 377 ... 530 531

Sin comentarios

Dell Vizioncore Manual de usuario Pagina 372