MOOSE is the monitoring system provided by POINT and FLIPS. The monitoring specification has been analysed to refactor the measurements into series. The full monitoring specification is available here:
network_resource measures the overall capacity of the network available to the platform for allocation to tenants. There are currently no metrics defined for this in the FLIPS monitoring specification, although we can envisage usage metrics such as bandwidth being part of this measurement.
SF Network Measurements measure aspects of network performance in relation to SFs deployed within the network. There are currently too many names for a node within the network and the following can be considered synonyms (SF, network element, node)
#### Media Service Measurements
**node_network_perf**
Common tags
node_network_perf provides the network measurement view for network elements. Network elements can be in the role of gateway, forwarding node, network attachment point, rendezvous, service, topology manager or user equipment as defined by the FLIPS monitoring specification. The measurements are made by the Mona monitoring agent.
* sfc – an orchestration template
* sfc_instance – an instance of the orchestration template
* sf_package – a SF type
* sf_instance – an instance of the SF type
* vm_instance – an authoritive copy of the SF instance
* server – a physical or virtual server for hosting VM instances
* location – the location of the server
##### Network Measurements
Network Measurements measure aspects of network performance in relation to VMs/containers.
The following fields need further analysis as they seem to relate to core ICN and buffering. These do not seem that relevant
Fields:
* BUFFER_SIZES_M
* BUFFER_SIZES_M
* FILE_DESCRIPTORS_TYPE_M
* HTTP_REQUESTS_FQDN_M
* MATCHES_NAMESPACE_M
* PATH_CALCULATIONS_NAMESPACE_M
* PACKET_JITTER_CID_M
* PUBLISHERS_NAMESPACE_M
* RX_BYTES_CID_M
* RX_BYTES_PORT_M
* RX_PACKETS_M
* RX_PACKETS_HTTP_M
* RXPACKETS_IP_M
* RX_PACKETS_IP_MULTICAST_M
* SUBSCRIBERS_NAMESPACE_M
* TX_BYTES_PORT_M
* TX_BYTES_CID_M
* TX_BYTES_HTTP_M
* TX_BYTES_IP_M
* TX_BYTES_IP_MULTICAST_M
* TX_PACKETS_PORT_M
* TX_PACKETS_HTTP_M
* TX_PACKETS_IP_M
* TX_PACKETS_IP_MULTICAST_M
Global Tags
**node_network_perf**
node_network_perf provides the network measurement view for network elements. Network elements can be in the role of gateway, forwarding node, network attachment point, rendezvous, service, topology manager or user equipment as defined by the FLIPS monitoring specification. The measurements are made by the Mona monitoring agent.
Questions
* Can a single value of jitter (e.g. avg jitter) be calculated from the set of measurements in PACKET_JITTER_CID_M message? What is the time period for the list of jitter measurements?
* What does CID actually mean?
*node_id: the network element id allocated to this surrogate
* sf_inst_id : the service function instance that this node represents in the case of surrogates
*sf_id : the service function type
*sfc_inst_id : the service function chain instance that this node is part of
*sfc_id : the service function chain type that this node is part of
*server_id : the server where the node is provisioned
The netnode_port series provides network measurements on host ports as defined by the FLIPS monitoring specification. The measurements are made by the Mona monitoring agent.
The netnode_port series provides network measurements on host ports as defined by the FLIPS monitoring specification.
SF Host Resource Measurements measures the host resources allocated to a service function deployed by the platform. All measurements have the following global tags to allow the data to be sliced and diced according to dimensions.
Global Tags
* node_id : the unique id of the network element
* sf_inst_id : the service function instance that this node represents in the case of surrogates
* sf_id : the service function type
* sfc_inst_id : the service function chain instance that this node is part of
* sfc_id : the service function chain type that this node is part of
* server_id : the server where the node is provisioned
* location : the location of the server
**node_host_resource**
*node_host_resource* measures host resources allocated to a node.
* node_id: the network element id allocated to this surrogate
* sf_inst_id : the service function instance that this node represents in the case of surrogates
* sf_id : the service function type
* sfc_inst_id : the service function chain instance that this node is part of
* sfc_id : the service function chain type that this node is part of
* server_id : the server where the node is provisioned
* location : the location of the server
Tags
* node_id: the network element id allocated to the topology manager
PATH_CALCULATIONS_NAMESPACE_M
**nap**
nap measurements are the platforms view on IP endpoints such as user equipment and services. A NAP is therefore the boundary of the platform. NAP measurements may need to be extended to provide more information on the relationship between clients and FQDN requests.
Fields
* CHANNEL_AQUISITION_TIME_M
* CMC_GROUP_SIZE_M
* NETWORK_LATENCY_FQDN_M
* RX _BYTES_HTTP_M
* RX _BYTES_IP_M
Global Tags
* node_id: the network element id allocated to this surrogate
* sf_inst_id : the service function instance that this node represents in the case of surrogates
* sf_id : the service function type
* sfc_inst_id : the service function chain instance that this node is part of
* sfc_id : the service function chain type that this node is part of
* server_id : the server where the node is provisioned
* location : the location of the server
Specific Tags
* coverage (tbc indicating the reach of the NAP)
**orchestrator**
Fields
* ???
Tags
nap measurements are the platforms view on IP endpoints such as user equipment and services. A NAP is therefore the boundary of the platform. NAP also measures aspects of co-incidental multicast performance
* node_id: the network element id allocated to the orchestrator
Questions
**clmc**
* What is the group id for CHANNEL_AQUISITION_TIME_M and how can this be related to FQDN of the content?
* what is the predefined time interval for CMC_GROUP_SIZE_M?
* How does NETWORK_LATENCY_FQDN_M relate to END_TO_END_LATENCY?
* How are multicast groups identified? i.e. "a request for FQDN within a time period", what's the content granularity here?
* HTTP_REQUESTS_FQDN_M says from an endpoint yet the measurement does not have a node id, it could be just the total number of requests for a FQDN, it which case it is very much like service request stats of a media service
Each SF developed by tenants will offer service specific usage and performance measurements. The fields in the measurements will be specific but the tags must include a predefined set of tags to allow series joins with SF Network and SF Host Resource measurements.
* CHANNEL_AQUISITION_TIME_M: avg time for all nodes in this group over sample period
* CMC_GROUP_SIZE_M: avg multicastgroup size over sample period
* NETWORK_FQDN_LATENCY: avg network latency over sample period
The actual measurements will be made by agents running on surrogate services which provide authoritative copies of SF instances deployed as part of an overall media service. Therefore the measurement series are named surrogate
**service**
Fields
* [developer defined]
Each SF developed will offer service specific usage and performance measurements.
