Skip to content
Snippets Groups Projects
Commit b07fd50a authored by Michael Boniface's avatar Michael Boniface
Browse files

update to docs

parent 1bd8bca3
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 59 additions and 59 deletions
docs/monitoring.md
+ 59
− 59
View file @ b07fd50a
......@@ -222,6 +222,61 @@ network_resource measures the overall capacity of the network available to the p
`network_resource,slice_id="",network_id="", bandwidth=(integer),X=(integer),Y=(integer),Z=(integer) timestamp`
#### Platform Measurements
The following fields need further analysis as they seem to relate to core ICN and buffering. These do not seem that relevant
* BUFFER_SIZES_M
* FILE_DESCRIPTORS_TYPE_M
* MATCHES_NAMESPACE_M
* PUBLISHERS_NAMESPACE_M
* SUBSCRIBERS_NAMESPACE_M
**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 also measures aspects of co-incidental multicast performance
Questions
* 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
* RX _BYTES_IP_MULTICAST_M
* TX_BYTES_IP_MULTICAST_M
* RX_PACKETS_HTTP_M
* TX_PACKETS_HTTP_M
* TX_BYTES_HTTP_M
* RX_PACKETS_IP_MULTICAST_M
* TX_PACKETS_IP_MULTICAST_M
* RX_BYTES_IP_M
* TX_BYTES_IP_M
`nap_node,<global_tags>,nodeId="", CHANNEL_AQUISITION_TIME_M, timestamp`
* Can we ignore the specific nodes and look at aggregate measurements associated with a multicast group?
* Here the assumption is that nodes are grouped around requests to access content idenified by hashes of FQDN.
`nap_multicast,<global_tags>,groupId="",fqdn="" CHANNEL_AQUISITION_TIME_M, CMC_GROUP_SIZE_M, NETWORK_FQDN_LATENCY timestamp`
* 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
**orch_media_service**
**orch_sfc_instance**
**orch_sf_instance**
**clmc**
#### Media Service Measurements
Common tags
......@@ -293,7 +348,7 @@ Tags
* destination_node_id
* link_type
#### SF Host Resource Measurements
##### Host Measurements
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.
......@@ -335,63 +390,7 @@ The resources allocated to a VM/Container
[[inputs.system]]
#### Platform Measurements
The following fields need further analysis as they seem to relate to core ICN and buffering. These do not seem that relevant
* BUFFER_SIZES_M
* FILE_DESCRIPTORS_TYPE_M
* MATCHES_NAMESPACE_M
* PUBLISHERS_NAMESPACE_M
* SUBSCRIBERS_NAMESPACE_M
**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 also measures aspects of co-incidental multicast performance
Questions
* 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
* RX _BYTES_IP_MULTICAST_M
* TX_BYTES_IP_MULTICAST_M
* RX_PACKETS_HTTP_M
* TX_PACKETS_HTTP_M
* TX_BYTES_HTTP_M
* RX_PACKETS_IP_MULTICAST_M
* TX_PACKETS_IP_MULTICAST_M
* RX_BYTES_IP_M
* TX_BYTES_IP_M
`nap_node,<global_tags>,nodeId="", CHANNEL_AQUISITION_TIME_M, timestamp`
* Can we ignore the specific nodes and look at aggregate measurements associated with a multicast group?
* Here the assumption is that nodes are grouped around requests to access content idenified by hashes of FQDN.
`nap_multicast,<global_tags>,groupId="",fqdn="" CHANNEL_AQUISITION_TIME_M, CMC_GROUP_SIZE_M, NETWORK_FQDN_LATENCY timestamp`
* 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
**orch_media_service**
**orch_sfc_instance**
**orch_sf_instance**
**clmc**
#### Service Measurements
##### Service Measurements
Each SF developed will offer service specific usage and performance measurements.
......@@ -403,4 +402,5 @@ Specific Tags
* cont_nav: the content requested
* cont_rep: the content representation requested
* user_id: the pseudonym of the user
\ No newline at end of file
* user_id: the pseudonym of the user
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment