Working with Metric Types

VMware Telco Cloud Service Assurance supports multiple metric types. The data collected uses out-of-the-box collectors including Domain Manager and MnR Gateway. All data collected is mapped to one of the VMware Telco Cloud Service Assurance metric type models.

Each metric type includes metadata that defines and describes the characteristics of each metric collected. The following is the JSON definition table for the standard parameters within each metric:

JSON	Description
collectorType	The collector or KPI type.
collectorInstance	The collector or KPI instance.
collectedTimestamp	The time (in milliseconds) when the metrics were collected by the collector or KPI. For example, 00:00:00 Jan 1, 1970 UTC.
processedTimestamp	Internal usage.
metricType	The type of metric. For example: Availability.
properties:	The properties of the metric. For example: Device Name, Entity Type, and so on.
dataSource	The IP address or host name of the data source.
deviceType	The type of the device. For example, a switch, firewall, or server).
deviceName	Instance name of the device.
entityType	The type of the entity in the device (for example, port, or interface) to which the below metrics belong.
Tags:	The tags define the properties that are set for all values in the scope.
model	The model of the device.
version	The version of the device.
customer	A customer or tenant identifier.
location	The location of the device.
city	The city in which the device is physically located.
address	The street address where the device is physically located.
zip	The postal code of the address where the device is located.
region	The region where the device is located.
deviceCoordinates	The geographical coordinates of the location where the device is located.

The following is an example of how the standard parameters appear within each metric:

{
  "collectorType" : "Kafka-Collector",
  "collectorInstance" : "KC-1",
  "collectedTimestamp" : 1573186658,
  "processedTimestamp" : 1573186658,
  "metricType" : "Availability",
  "properties" : {
    "dataSource" : "10.100.10.10",
    "deviceType" : "Router",
    "deviceName" : "Router-1.1.1.1",
    "entityType" : "Interface",
    "entityName" : "Interface-113/m1"
 },
  "metrics" : {
    "Availability":     "100",
    "Reachability":     "100"
 },
  "tags" : {
    "model" : "CAT-100",
   "version" : "1.0.0.1",
    "customer" : "customer-1",
    "location" : "main street",
    "city" : "Zurich",
    "address" : "abc",
    "zip" : "90882",
    "region" : "region-1", 
    "deviceCoordinates" : "45.444348, -75.693934"
 }
}

Note: Using a Tool Data Set – You can use third-party vendors to collect metrics, for example, Metricbeat or OpenStack API.