Common part of the various VLDs. Uniquely identifies a VLD in the parent descriptor. For VnfVirtualLinkDesc, the parent descriptor is the VNFD. For NsVirtualLinkDesc, the parent descriptor is the NSD. Note: the description of this class are different in ETSI GS NFV IFA 011 and ETSI GS NFV IFA 014. The present definition merges the 2 definitions. Specifies the protocol exposed by a VL and the flow pattern supported by the VL. Specifies test access facilities expected on the VL (e.g. none, passive monitoring, or active (intrusive) loopbacks at endpoints. Provides human-readable information on the purpose of the VL (e.g. control plane traffic). A functional block within a network infrastructure that has well-defined external interfaces and well-defined functional behaviour. NOTE: In practical terms, a Network Function is today often a network node or physical appliance A set of connection points along with the connectivity relationship between them and any associated target performance metrics (e.g. bandwidth, latency, QoS). NOTE: The Virtual Link can interconnect two or more entities (VNF components, VNFs, or PNFs) and it is supported by a Virtual Network (VN) of the NFVI. Link ports of this VL. Identifier of the virtual link instance. An intelligent or human readable name of the virtual link instance. Additional intelligent or human readable name of the virtual link instance. Generic description of the type of Virtual Link Role in the network this virtual link will be providing English description of the function this specific virtual link will be providing virtual link assigned (actual) bandwidth provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems valid value example: PROVISIONED, PREPROVISIONED, CAPPED Administrative status of the virtual link Specifies the minimum bitrate requirements for the virtual link Specifies the maximum bitrate requirements for the virtual link Indicates whether DHCP is enabled Indicates whether VLAn transparent mode is supported Indicates whether Trunk Mode is enabled Outer vlan tag Inner vlan tag Identified the layerProtocol and flowPattern used by the virtual link Represents the port of the link. CP to be connected to this link port. Parent for all connection point classes. Identifier of the connection point instance. Name of the Cp instance. alternative name of the Cp instance. Generic description of the type of Cp Role in the network this Cp will be providing English description of the function this specific Cp will be providing Cp description Cp (max? assigned?) bandwidth Cp assigned (actual) bandwidth provisioning status, used as a trigger for operational monitoring of this resource by service assurance systems valid value example: PROVISIONED, PREPROVISIONED, CAPPED Administrative status of the connection point. Protocol used by the Cp Indicator whether the Cp is in trunk mode Type of address: MAC address or IP address Only present when addressType is MAC address Only present when addressType is IP address

Fields specific to fault events. Fill in attribute defs and check attribute multiplicity namedHashMap [ ] - The namedHashmap datatype is a hashMap which is associated with and described by a name. name - Name for the array of name-value pairs. hashMap - One or more key:value pairs. Note: in ATTServiceSpecification - VesEventListener v5.4.1 type = field []. The SecurityParameters contains the signature of a NSD, VLD, PNFD or VNFFGD instance together with information required to validate the signature. Provides the signature of the signed part of the descriptor. Identifies the algorithm used to compute the signature. Provides a certificate or a reference to a certificate to validate the signature. NOTE: Cardinality of 0 corresponds to the case where the certificate is provided by means outside the NSD Specifies whether the rule is an affinity rule or an anti-affinity rule. Specifies the scope of the rule. The LinkBitrateRequirements datatype describes the requirements in terms of bitrate for a Virtual Link. Specifies the throughput requirement of the link (e.g. bitrate of E-Line, root bitrate of E-Tree, aggregate capacity of E-LAN). Specifies the throughput requirement of leaf connections to the link when applicable to the connectivity type (e.g. for E-Tree and E-LAN branches). NOTE: The present document does not specify the means to declare different bitrate requirements for leaf connections (e.g. E-LAN leaves). This primitive type defines the version of an element. type string { pattern '[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}'; } A Universally Unique IDentifier in the string representation defined in RFC 4122. The canonical representation uses lowercase characters. The following is an example of a UUID in string representation: f81d4fae-7dec-11d0-a765-00a0c91e6bf6 "; reference "RFC 4122: A Universally Unique IDentifier (UUID) URN Namespace" type string; The uri type represents a Uniform Resource Identifier (URI) as defined by STD 66. Objects using the uri type MUST be in US-ASCII encoding, and MUST be normalized as described by RFC 3986 Sections 6.2.1, 6.2.2.1, and 6.2.2.2. All unnecessary percent-encoding is removed, and all case-insensitive characters are set to lowercase except for hexadecimal digits, which are normalized to uppercase as described in Section 6.2.2.1. The purpose of this normalization is to help provide unique URIs. Note that this normalization is not sufficient to provide uniqueness. Two URIs that are textually distinct after this normalization may still be equivalent. Objects using the uri type may restrict the schemes that they permit. For example, 'data:' and 'urn:' schemes might not be appropriate. A zero-length URI is not a valid URI. This can be used to express 'URI absent' where required. In the value set and its semantics, this type is equivalent to the Uri SMIv2 textual convention defined in RFC 5017. reference "RFC 3986: Uniform Resource Identifier (URI): Generic Syntax RFC 3305: Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations RFC 5017: MIB Textual Conventions for Uniform Resource Identifiers (URIs)" Primitive type describing a rule. This primitive type is a superset of the standard UML numbering primitives, e.g. Integer and Real. priority - processing priority. Identifies the protocol this VL gives access to (Ethernet, MPLS, ODU2, IPV4, IPV6, Pseudo-Wire). Identifies the flow pattern of the connectivity (Line, Tree, Mesh). The L3AddressData information element supports providing information about Layer 3 level addressing scheme and parameters applicable to a CP. Specify if the address assignment is the responsibility of management and orchestration function or not. If it is set to True, it is the management and orchestration function responsibility. Specify if the floating IP scheme is activated on the CP or not. Define address type. NOTE: The address type should be aligned with the address type supported by the layerProtocol attribute of the parent Cpd. Minimum number of IP addresses to be assigned based on this L3AddressData information element. Specify if the MAC address assignment is the responsibility of management and orchestration function or not. If it is set to True, it is the management and orchestration function responsibility. If it is set to False, it will be provided by an external entity, e.g. OSS/BSS. object - objects are model elements that represent instances of a class or of classes key - the key datatype is a tuple which provides the name of a key along with its value and relative order. keyName - Name of the key. keyOrder - Relative sequence or order of the key (with respect to other keys). keyValue - Value of the key. The LinkBitrateRequirements information element describes the requirements in terms of bitrate for a VL. Throughput requirement of the link (e.g. bitrate of E-Line, root bitrate of E-Tree, aggregate capacity of E-LAN). Throughput requirement of leaf connections to the link when applicable to the connectivity type (e.g. for E-Tree and E?LAN branches). NOTE: The present document does not specify the means to declare different bitrate requirements for leaf connections (e.g. E-LAN leaves). Identifies the protocol this VL gives access to An ONAP event is an aggregation of a header and a message. Event messages may be published to a message broker by service instances, resource instances, or ONAP platform components. Service or resource instances may be in support of network infrastructure or customer services. Interested platforms may subscribe to events on the message broker (e.g. Centralized Testing Platform CTP) may see an event on a service VNF instance and perform an automated test as part of a closed loop management policy. Events are unique and distinguishable from one another. ONAP event messages are serialized as a unicode ASCII character string which may be formatted as JSON, XML, etc... Appropriate schemas will be supplied. commonEventHeader - Fields common to all events. commonEventBody - Heartbeat is an event header only with no event body [0..1] commonEventHeader - Fields common to all events. domain - Event domain enumeration: ‘fault’, ‘heartbeat’, ‘measurementsForVfScaling’, ‘mobileFlow’, ‘other’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’ eventId -Event key that is unique to the event source. The key must be unique within notification life cycle similar to EventId from 3GPP. It could be a sequential number, or a composite key formed from the event fields, such as domain_sequence. The eventId should not include whitespaces. For fault events, eventId is the eventId of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, eventId must be the same as the initial alarm (along with the same startEpochMicrosec but with a different sequence number). eventName - Unique event name. To prevent naming collisions, eventName sent as part of the commonEventHeader, should conform to the following naming convention designed to summarize the purpose and type of the event, and to ensure the uniqueness of the eventName: {DomainAbbreviation}_{NamingCode or ApplicationPlatform}_{DescriptionOfInfoBeingConveyed} Domain abbreviations are derived from the ‘domain’ field in the commonEventHeader, as specified below: ‘Fault’ for the fault domain ‘Heartbeat’ for the heartbeat domain ‘Measurement’ for the measurements domain ‘MobileFlow’ for the mobileFlow domain ‘Other’ for the other domain ‘PnfReg’ for the pnfRegistration domain ‘SipSignaling’ for the sipSignaling domain ‘StateChange’ for the stateChange domain ‘Syslog’ for the syslog domain ‘Tca’ for the thresholdCrossingAlert domain ‘VoiceQuality’ for the voiceQuality domain eventType - Needs to determine the source generating the event. The valid values are: ‘applicationVnf’, ‘guestOS’, ‘hostOS’, ‘platform’ applicationVNF: When the event is related to the VNF application. guestOS: When the event is related to the Operating System of the VM where the VNF is running on. platform: When the event is related to the platform, hardware of where a VNF might be running on (including Jericho Cisco NCS Switch) hostOS: When the event is related to the operating system of the hardware lastEpochMicrosec - the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds nfcNamingCode - Network function component type: 3 characters (aligned with vfc naming standards) nfNamingCode - Network function type: 4 characters (aligned with Vnf naming standards). priority - Processing priority enumeration: ‘High’, ‘Medium’, ‘Normal’, ‘Low’ reportingEntityId - UUID identifying the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. Note: the AT&T internal enrichment process shall ensure that this field is populated. The reportingEntityId is an id for the reportingEntityName. See reportingEntityName for more information. reportingEntityId - UUID identifying the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. Note: the AT&T internal enrichment process shall ensure that this field is populated. The reportingEntityId is an id for the reportingEntityName. See reportingEntityName for more information. reportingEntityName - Name of the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. reportingEntityName - Name of the entity reporting the event or detecting a problem in another xnf/vm or pnf which is experiencing the problem. May be the same as the sourceName. For synthetic events generated by DCAE, it is the name of the app generating the event. sequence - Ordering of events communicated by an event source instance (or 0 if not needed) sequence - Ordering of events communicated by an event source instance (or 0 if not needed) sourceId - UUID identifying the entity experiencing the event issue, which may be detected and reported by a separate reporting entity Note: the AT&T internal enrichment process shall ensure that this field is populate). The sourceId is an id for the sourceName. See sourceName for more information. sourceId - UUID identifying the entity experiencing the event issue, which may be detected and reported by a separate reporting entity Note: the AT&T internal enrichment process shall ensure that this field is populate). The sourceId is an id for the sourceName. See sourceName for more information. sourceName - Name of the entity experiencing the event issue, which may be detected and reported by a separate reporting entity. The sourceName identifies the device for which data is collected. A valid sourceName must be inventoried in A&AI. If sourceName is a xNFC or VM, then the event must be reporting data for that particular xNFC or VM. If the sourceName is a xNF, comprised of multiple xNFCs, the data must be reported/aggregated at the xNF leveI. Data for individual xNFC must not be included in the xNF sourceName event. sourceName - Name of the entity experiencing the event issue, which may be detected and reported by a separate reporting entity. The sourceName identifies the device for which data is collected. A valid sourceName must be inventoried in A&AI. If sourceName is a xNFC or VM, then the event must be reporting data for that particular xNFC or VM. If the sourceName is a xNF, comprised of multiple xNFCs, the data must be reported/aggregated at the xNF leveI. Data for individual xNFC must not be included in the xNF sourceName event. startEpochMicrosec - the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds. For measurements and heartbeats, where events are collected over predefined intervals, startEpochMicrosec shall be rounded to the nearest interval boundary (e.g., the epoch equivalent of 3:00PM, 3:10PM, 3:20PM, etc…). For fault events, startEpochMicrosec is the timestamp of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, startEpochMicrosec must be the same as the initial alarm (along with the same eventId and an incremental sequence number). For devices with no timing source (clock), the default value will be 0 and DCAE collector will replace it with Collector time stamp (when event is received). startEpochMicrosec - the earliest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds. For measurements and heartbeats, where events are collected over predefined intervals, startEpochMicrosec shall be rounded to the nearest interval boundary (e.g., the epoch equivalent of 3:00PM, 3:10PM, 3:20PM, etc…). For fault events, startEpochMicrosec is the timestamp of the initial alarm; if the same alarm is raised again for changed, acknowledged or cleared cases, startEpochMicrosec must be the same as the initial alarm (along with the same eventId and an incremental sequence number). For devices with no timing source (clock), the default value will be 0 and DCAE collector will replace it with Collector time stamp (when event is received). timeZoneOffset - offset to/from GMT to indicate local timezone for device. Example: +4, -5 version - Version of the event header eventBody, if it exists, will contain exactly one of the following depending on the type of event as specified by the eventHeader domain field. - faultField - heartbeat - measurementFields - mobileFlowFIelds - notificationFields - otherfields - pnfRegistrationFields - sipSignalingFields - stateChangeFields - syslogFields - thresholdCrosssingAlertFields - voiceQualityFields faultFields - Fields specific to fault events. Fields specific to fault events. measurementsFields - Fields specific to measurement events. mobileFlowFields - Fields specific to mobilityFlow events. notificationFields - Fields specific to notification events. otherFields - Fields specific to other types of events. pnfRegistrationFields - Fields specific to pnfRegistration events. sipSignalingFields - Fields specific to sipSignaling events. stateChangeFields - Fields specific to state change events. syslogFields - Fields specific to syslog events. thresholdCrossingAlertFields - Fields specific to thresholdCrossingAlert events. voiceQualityFields - Fields specific to voiceQuality events. codecsInUse - the codecsInUse datatype consists of the following fields describing the number of times an identified codec was used over the measurementInterval codecIdentifer - Description of the codec. numberInUse - Number of such codecs in use. faultFields - Fields specific to fault events alarmAdditionalInformation - additional Information related to Alarm, such as Repair Action, Remedy code. May by serialized alarm payload: varbind list, original syslog message, notification parameters, etc. when event is generated via other means, should provide raw detail out of element. alarmCondition - Short name of the alarm/problem, like trap name. Could be of SPECIFIC_PROBLEM list: (x733_SpecificProblems). Should be string to avoid duplicate dictionary translation. This should be a one word. Indicates the Alarm Condition as reported by the device. Should be string to avoid duplicate dictionary translation. This would be a alarm description. Data from probableCause (3GPP and MTOSI) would be an alarm summary. alarmInterfaceA - Provide port or channel or interface information when alarm is related with interface faults. Could be card/port, or channel, or interface name. Would represent the interface number the event on the sourceName is reported against, so alarm generated on the device interface could be identified against the far side (alarmInterfaceZ) based on logical or physical topology rather than having the information embedded somewhere else requiring regular expression extract. eventCategory - Event category. For example: ‘license’, ‘link’, ‘routing’, ‘security’, ‘signaling’ eventSeverity - Event severity enumeration. severity enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’ eventSourceType - Provide the type of element the Source might be. This can be network function specific, or application specific. Examples: other, router, switch, host, card, port, slotThreshold, portThreshold, virtual machine, etc… Could also be PCRF, MMSC, NEM, MME, ENB, etc... faultFieldsVersion - version of the faultFields block. specificProblem - short name of the alarm/problem, like trap name. Could be of SPECIFIC_PROBLEM list: (x733_SpecificProblems). Should be string to avoid duplicate dictionary translation. This should be a one word. Example: LinkDown, BFDSessionDown, etc…. SpecificProblem (3GPP) or X733_SpecificProblem (MTOSI) vfStatus - Used to report on VF status, both to indicate success/failure of start/stop/prepare to terminate events, but also to allow VF to request termination after unrecoverable errors. Enumeration; valid values are - Idle - Active - Preparing to terminate - Ready to terminate - Requesting termination additionalFields - Additional expansion fields if needed. additionalFields - Additional expansion fields if needed. heartbeatFieldVersion - version of the heartbeatFields block. heartbeatInterval - current heartbeatInterval in seconds. measurementFields - Fields specific to measurement events additionalFields - Additional measurement fields if needed. additionalMeasurements - Array of named hashMap if needed. additionalObjects - Array of JSON objects described by name, schema and other meta-information, if needed. codecUsageArray - array of codecs in use. concurrentSessions - Peak concurrent sessions for the VM or VNF (depending on the context) over the measurementInterval. configuredEntities - Depending on the context over the measurementInterval: peak total number of users, subscribers, devices, adjacencies, etc., for the VM, or peak total number of subscribers, devices, etc., for the VNF cpuUsageArray - Usage of an array of CPUs diskUsageArray - Usage of an array of disks. featureUsageArray - The hashMap key should identify the feature, while the value defines the number of times the identified feature was used. filesystemUsageArray - Filesystem usage of the VM on which the VNFC reporting the event is running. hugePagesArray - Array of metrics on hugePages ipmiArray - Array of intelligent platform management interface metrics. latencyDistribution - Array of integers representing counts of requests whose latency in milliseconds falls within per-VNF configured ranges; where latency is the duration between a service request and its fulfillment. loadArray - Array of system load metrics machineCheckExceptionArray - Array of machine check exceptions. meanRequestLatency - Mean seconds required to respond to each request for the VM on which the VNFC reporting the event is running. measurementFieldsVersion - version of the measurementFields block. measurementInterval - Interval over which the usage measures are being reported. The allowed intervals to be integral number of minutes that evenly divide 60 minutes. So, allowed intervals would be 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, and 60 minutes or the parameter to be specified in seconds (e.g., 60, 120, 180, 240, 300, 360, 600, 720, 900, 1200, 1800, and 3600 seconds). memoryUsageArray - Memory usage of an array of VMs nfcScalingMetric - Represents busy-ness of the network function from 0 to 100 as reported by the nfc. nicPerformanceArray - Performance metrics of an array of network interface cards. numberOfMediaPortsInUse - Number of media ports in use. processStatsArray - Array of metrics on system processes requestRate - Peak request rate per second, for the VM over the measurementInterval Fields specific to mobility flow events additionalFields - Additional mobileFlow fields if needed. applicationType - Application type inferred applProtocolType - Application protocol. applProtocolVersion - Application version. cid - Cell Id. connectionType - Abbreviation referencing a 3GPP reference point e.g., S1-U, S11, etc. ecgi - Evolved Cell Global Id. flowDirection - Flow direction, indicating if the reporting node is the source of the flow or destination for the flow. gtpPerFlowMetrics - Mobility GTP Protocol per flow metrics. gtpProtocolType - GTP protocol gtpVersion - GTP protocol version. httpHeader - HTTP request header, if the flow connects to a node referenced by HTTP. imei - IMEI for the subscriber UE used in this flow, if the flow connects to a mobile device. imsi - IMSI for the subscriber UE used in this flow, if the flow connects to a mobile device ipProtocolType - IP protocol type e.g., TCP, UDP, RTP... ipVersion - IP protocol version e.g., IPv4, IPv6 lac - Location area code. mcc - Mobile country code. mnc - Mobile network code. mobileFlowFieldsVersion - Version of the mobileFlowFields block. msisdn - MSISDN for the subscriber UE used in this flow, as an integer, if the flow connects to a mobile device. otherEndpointIpAddress - IP address for the other endpoint, as used for the flow being reported on. Note: current data type (String) may be changed to Common Resource Datatype L3AddressData. =[gh]= otherEndpointPort - IP Port for the reporting entity, as used for the flow being reported on otherFunctionalRole - Functional role of the other endpoint for the flow being reported on e.g., MME, S-GW, P-GW, PCRF... rac - Routing area code radioAccessTechnology - Radio Access Technology e.g., 2G, 3G, 4G and 5G. (GSM, UMTS, LTE, 5G) reportingEndpointIpAddr - IP address for the reporting entity, as used for the flow being reported on. Note: current data type (String) may be changed to Common Resource Datatype L3AddressData. =[gh]= reportingEndpointPort - IP port for the reporting entity, as used for the flow being reported on. sac - Service area code samplingAlgorithm - Integer identifier for the sampling algorithm or rule being applied in calculating the flow metrics if metrics are calculated based on a sample of packets, or 0 if no sampling is applied. tac - Transport area code tunnelId - Tunnel identifier vlanId - VLAN identifier used by this flow namedHashMap [ ] - The namedHashmap datatype is a hashMap which is associated with and described by a name. name - Name for the array of name-value pairs. arrayOfFields - Name-value pairs. Note: in ATTServiceSpecification - VesEventListener v5.4.1 type = field []. Fields specific to notification events additionalFields - Additional notification fields if needed. arrayOfNamedHashMap - Array of named hashMaps changeContact - Identifier for a contact related to the change. changeIdentifier - System or session identifier associated with the change. changeType - Identifies what has changed for entity. e.g., auto discovery. configuration changed, capability added, capability removed, capability changed, etc. newState - new state of the entity, for Configuration it could be if change was complete or partial etc. For example: "inService", "outOfService", "maintenance", "completed", "partial" (for configuration changes) notificationFieldsVersion - Version of the notificationFields block. oldState - Previous state of the entity. For example: "inService", "outOfService", "maintenance" stateInterface - Card or port name of the entity that changed state. otherFields - The otherFields datatype defines fields for events belonging to the 'other' domain of the commonEventHeader domain enumeration. arrayOfNamedHashMap - Array of named name-value-pair arrays. hashMap - Array of name-value pairs. jsonObjects - Array of JSON objects described by name, schema and other meta-information. otherFieldsVersion - Version of the otherFields block. sipSignalingFields - The sipSignalingFields datatype communicates information about SIP signaling messages, parameters and signaling state. additionalInformation - Additional sipSignalling fields. compressedSip - The full SIP request/response including headers and bodies. correlator - Constant across all events on this call. localIpAddress - IP address on VNF. Note: current data type (String) may be changed to Common Resource Datatype L3AddressData. =[gh]= localPort - Port on VNF. remoteIpAddress - IP address of peer endpoint. Note: current data type (String) may be changed to Common Resource Datatype L3AddressData. =[gh]= remotePort - Port of peer endpoint sipSignalingFieldsVersion - Version of the sipSignalingFields block as “#.#” where # is a digit; see section 1 for the correct digits to use. summarySip - The SIP Method or Response (‘INVITE’, ‘200 OK’, ‘BYE’, etc). vendorNfNameFields - Vendor, NF and nfModule names. stateChangeFields - Fields specific to state change events. Additional stateChange fields if needed New state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’ Previous state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’ Version of the stateChangeFields block as “#.#” where # is a digit; see section 1 for the correct digits to use. Card or port name of the entity that changed state syslogFields - Fields specific to syslog events. additionalFields - Additional pnfRegistration fields if needed. lastEpochMicrosec - the latest unix time aka epoch time associated with the event from any component--as microseconds elapsed since 1 Jan 1970 not including leap seconds Defines the network address type. Array of named hashMaps Array of named hashMaps cpuUsage - The cpuUsage datatype defines the usage of an identifier CPU. cpuUsageNice - Percentage of time spent running user space processes that have been "niced". cpuSwapWaitTime - Swap wait time, in milliseconds over the measurementInterval. cpuOverheadAvg - The overhead demand above available allocations and reservations, in milliseconds over the measurementInterval. cpuLatencyAverage - Percentage of time the VM is unable to run because it is contending for access to the physical CPUs. cpuIdle - Percentage of CPU time spent in the idle task. cpuIdentifier - CPU Identifier cpuDemandPct - CPU demand as a percentage of the provisioned capacity. cpuDemandMhz - CPU demand in megahertz (MHz). For comparison in computing powers, processors of "x Core CPU @ y GHz" (like 6 Core CPU @ 2 GHz) are commonly converted into scalar values in MHz. With CPU demand in MHz, choosing an adequate processor to add becomes easy. cpuDemandAvg - The total CPU time that the VNF/VNFC/VM could use if there is no contention, in milliseconds. cpuCapacityContention - The amount of time the CPU cannot run due to centention, in milliseconds. cpuUsageSoftIrq - Percentage of time spent handling soft irq interrupts. cpuUsageSteal - Percentage of time spent in involuntary wait which is neither user, system or idle time and is effectively time that went missing. cpuUsageSystem - Percentage of time spent on system tasks running the kernel. cpuUsageUser - Percentage of time spent running un-niced user space processes. cpuWait - Percentage of CPU time spent waiting for I/O operations to complete. percentUsage - Aggregate CPU usage of the virtual machine on which the VNFC reporting the event is running. diskUsage - The diskUsage datatype defines the usage of a disk device. diskBusResets - The number of bus resets in the performance interval. diskCommandsAborted - Number of disk commands aborted over the measurementInterval. diskCommandsAvg - Average number of commands per second over the measurementInterval. diskFlushRequests - Total flush requests of the disk cache over the measurementInterval. diskFlushTime - Milliseconds spent on disk cache flushing over the measurementInterval. diskIdentifier - Disk Identifier. diskIoTimeLast - Milliseconds spent doing input/output operations over 1 sec; treat this metric as a device load percentage where 1000ms matches 100% load; provide the last value measurement within the measurement interval. diskIoTimeMin - Milliseconds spent doing input/output operations over 1 sec; treat this metric as a device load percentage where 1000ms matches 100% load; provide the minimum value measurement within the measurement interval. diskMergedReadAvg - Number of logical read operations that were merged into physical read operations, e.g., two logical reads were served by one physical disk access; provide the average measurement within the measurement interval. diskMergedReadLast - Number of logical read operations that were merged into physical read operations, e.g., two logical reads were served by one physical disk access; provide the last value measurement within the measurement interval. diskMergedReadMax - Number of logical read operations that were merged into physical read operations, e.g., two logical reads were served by one physical disk access; provide the maximum value measurement within the measurement interval. diskMergedReadMin - Number of logical read operations that were merged into physical read operations, e.g., two logical reads were served by one physical disk access; provide the minimum value measurement within the measurement interval. diskMergedWriteAvg - Number of logical write operations that were merged into physical write operations, e.g., two logical writes were served by one physical disk access; provide the average measurement within the measurement interval diskMergedWriteLast - Number of logical write operations that were merged into physical write operations, e.g., two logical writes were served by one physical disk access; provide the last value measurement within the measurement interval. diskMergedWriteMax - Number of logical write operations that were merged into physical write operations, e.g., two logical writes were served by one physical disk access; provide the maximum value measurement within the measurement interval. diskMergedWriteMin - Number of logical write operations that were merged into physical write operations, e.g., two logical writes were served by one physical disk access; provide the minimum value measurement within the measurement interval. diskOctetsReadAvg - Number of octets per second read from a disk or partition; provide the average measurement within the measurement interval. diskOctetsReadLast - Number of octets per second read from a disk or partition; provide the last measurement within the measurement interval diskOctetsReadMax - Number of octets per second read from a disk or partition; provide the maximum measurement within the measurement interval. diskOctetsReadMin - Number of octets per second read from a disk or partition; provide the minimum measurement within the measurement interval. diskOctetsWriteAvg - Number of octets per second written to a disk or partition; provide the average measurement within the measurement interval. diskOctetsWriteLast - Number of octets per second written to a disk or partition; provide the last measurement within the measurement interval. diskOctetsWriteMax - Number of octets per second written to a disk or partition; provide the maximum measurement within the measurement interval. diskOctetsWriteMin - Number of octets per second written to a disk or partition; provide the minimum measurement within the measurement interval. diskOpsReadAvg - Number of read operations per second issued to the disk; provide the average measurement within the measurement interval. diskOpsReadLast - Number of read operations per second issued to the disk; provide the last measurement within the measurement interval. diskOpsReadMax - Number of read operations per second issued to the disk; provide the maximum measurement within the measurement interval. diskOpsReadMin - Number of read operations per second issued to the disk; provide the minimum measurement within the measurement interval. diskOpsWriteAvg - Number of write operations per second issued to the disk; provide the average measurement within the measurement interval. diskOpsWriteLast - Number of write operations per second issued to the disk; provide the last measurement within the measurement interval. diskOpsWriteMax - Number of write operations per second issued to the disk; provide the maximum measurement within the measurement interval. diskOpsWriteMin - Number of write operations per second issued to the disk; provide the minimum measurement within the measurement interval. diskPendingOperationsAvg - Queue size of pending I/O operations per second; provide the average measurement within the measurement interval. diskPendingOperationsLast - Queue size of pending I/O operations per second; provide the last measurement within the measurement interval. diskPendingOperationsMax - Queue size of pending I/O operations per second; provide the maximum measurement within the measurement interval. diskPendingOperationsMin - Queue size of pending I/O operations per second; provide the minimum measurement within the measurement interval. diskReadCommandsAvg -Average number of read commands issued per second to the disk over the measurementInterval. diskTime - Nanoseconds spent on disk cache reads/writes within the measurementInterval. diskTimeReadAvg - Milliseconds a read operation took to complete; provide the average measurement within the measurement interval. diskTimeReadLast - Milliseconds a read operation took to complete; provide the last measurement within the measurement interval. diskTimeReadMax - Milliseconds a read operation took to complete; provide the maximum measurement within the measurement interval. diskTimeReadMin - Milliseconds a read operation took to complete; provide the minimum measurement within the measurement interval. diskTimeWriteAvg - Milliseconds a write operation took to complete; provide the average measurement within the measurement interval. diskTimeWriteLast - Milliseconds a write operation took to complete; provide the last measurement within the measurement interval. diskTimeWriteMax - Milliseconds a write operation took to complete; provide the maximum measurement within the measurement interval. diskTimeWriteMin - Milliseconds a write operation took to complete; provide the minimum measurement within the measurement interval. diskTotalReadLatencyAvg - The average amount of time taken for a read from the perspective of a Guest OS. This is the sum of Kernel Read Latency and Physical Device Read Latency in milliseconds over the measurement interval. diskTotalWriteLatencyAvg - The average amount of time taken for a write from the perspective of a Guest OS. This is the sum of Kernel Write Latency and Physical Device Write Latency in milliseconds over the measurement interval. diskWriteCommandsAvg - Average number of write commands issued per second to the disk during the collection interval. ephemeralConfigured - Configured ephemeral storage capacity in GB. filesystemName - File system name. blockConfigured - Configured block storage capacity in GB. blockIops - Block storage input-output operations per second. blockUsed - Used block storage capacity in GB. ephemeralIops - Ephemeral storage input-output operations per second. ephemeralUsed - Used ephemeral storage capacity in GB. The hugePages datatype provides metrics on system hugePages bytesFree - Number of free hugePages in bytes. bytesUsed - Number of used hugePages in bytes. hugePagesIdentifier - HugePages identifier percentFree - Number of free hugePages in percent. percentUsed - Number of used hugePages in percent. vmPageNumberFree - Number of free hugePages in numbers. vmPageNumberUsed - Number of used hugePages in numbers. jsonObject - The jsonObject datatype provides a JSON object schema, name and other meta-information along with one or more object instances that conform to the schema. objectInstances - Contains one or more instances of the JSON object. objectName - Name of the json object. objectSchema - JSON schema for the object. objectSchemaUrl - URL to the JSON schema for the object. nfSubscribedObjectName - Name of the object associated with the nfSubscriptionId. nfSubscriptionId - Identifies an OpenConfig telemetry subscription on a network function, which configures the network function to send complex object data associated with the jsonObject. jsonObjectInstance [ ] - The jsonObjectInstance datatype provides meta-information about an instance of a jsonObject along with the actual object instance. jsonObject - Optional recursive specification on jsonObject objectInstance - Contains an instance conforming to the jsonObject schema objectInstanceEpochMicrosec - the unix time, aka epoch time, associated with this objectInstance--as microseconds elapsed since 1 Jan 1970 not including leap seconds. objectKeys - An ordered set of keys that identifies this particular instance of jsonObject (e.g., that places it in a hierarchy). domain - Event domain enumeration: ‘fault’, ‘heartbeat’, ‘measurementsForVfScaling’, ‘mobileFlow’, ‘other’, ‘sipSignaling’, ‘stateChange’, ‘syslog’, ‘thresholdCrossingAlert’, ‘voiceQuality’ vendorNfNameFields - The vendorNfNameFields provides vendor, nf and nfModule identifying information. vendorName - Network function vendor name. nfModuleName - Name of the nfModule generating the event. nfName - Name of the network function generating the event arrayOfJsonObject - The arrayOfJsonObject datatype provides an array of json objects, each of which is described by name, schema and other meta-information. arrayOfJsonObject - arrayOfJsonObject datatype provides an array of json objects, each of which is described by name, schema and other meta-information.