Tracker Consistency Checks

You are here:-, vScope Features-Tracker Consistency Checks

In vScope v2.3.0 we introduce a new type of Tracker Computations which measure the consistency of a certain metric in the datacenter. vScope v2.3.0 comes with a variety of new consistency checks. Let’s look at a few examples:

Example1: (preloaded)
Detect the consistency of DNS Settings across the datacenter

There is a predefined Tracker case which is triggered if the configured DNS server settings differ between servers in the datacenter.

This type of analysis only takes one parameter into consideration, the consistency of the tag “DNS Servers”

DNS_ConsistencyThis example investigate settings across the whole datacenter, but the case can easily narrowed down to a smaller subset of servers. Just press Edit Case to modify the case.

Example2: (preloaded)

Firmware consistency between VMware Hosts in each Cluster

This example, which also is predefined in Tracker, investigates the consistency of ESX-firmware within each VMware Cluster. The case is triggered if hosts in a cluster run different ESX-versions.

This type of analysis only takes two parameter into consideration, the consistency of the tag “OS” within each group of “Clusters”.

Cluster_Consistency

Example 3: (Build yourself)
Consistency between BillingIDs and Customers in a hosted datacenter

This case is an attempt to increase billing quality in a hosted datacenter. The Tracker Case checks the consistency between BillingID and Customer, to make sure that the BillingID-tag is correct everywhere.

This example is not predefined in Tracker, but can easily be built.

First, start creating a case and use the Tracker Computation as shown below. Use tag names appropriate to your setup.

Tracker_editor_billingThe result from this Tracker case should look like the following, in case an in-consistency is found. In this example one can see that two of the servers are tagged with BillingID 410000 while all the others have 210000, which could have been a human error leading to incorrect billing.

Billing _consistency

2018-01-02T21:55:50+00:00