docs: Clarity on subinterfaces

Author: tomclark0

doc/source/configuration/monitoring.rst

@@ -172,8 +172,8 @@ information appropiate to your cloud and re-deploy.
 
 Friendly Network Names
 =======================
-For operators that prefer to see descriptive or friendly interface names the 
-following play can be run. This takes network names as defined in kayobe and 
+For operators that prefer to see descriptive or friendly interface names the
+following play can be run. This takes network names as defined in kayobe and
 relabels the devices/interfaces in Prometheus to make use of these names.
 
 **Check considerations and known limitations to see if this is suitable in any
@@ -189,38 +189,40 @@ To enable the change:
     kayobe playbook run etc/kayobe/ansible/prometheus-network-names.yml
     kayobe overcloud service reconfigure --kt prometheus
 
-This first generates a template based on the prometheus.yml.j2 
+This first generates a template based on the prometheus.yml.j2
 ``etc/kayobe/ansible/`` and which is further templated for use with
 kolla-ansible.
 This is then rolled out via service reconfigure.
 
 
-This helps Prometheus provide insights that can be more easily understood by 
+This helps Prometheus provide insights that can be more easily understood by
 those without an intimate understanding of a given site. Prometheus Node
 Exporter and cAdvisor both provide network statistics using the
 interface/device names. This play causes Prometheus to relabel these fields to
- human readable names based on the networks as defined in kayobe 
+ human readable names based on the networks as defined in kayobe
  e.g. bond1.1838 may become storage_network.
 
-The default labels are preserved with the prefix ``original_``. 
+The default labels are preserved with the prefix ``original_``.
 
-* For node_exporter, ``device`` is then used for network names, while 
+* For node_exporter, ``device`` is then used for network names, while
   ``original_device`` is used for the interface itself.
-* For cAdvisor, ``interface`` is used for network names, and 
+* For cAdvisor, ``interface`` is used for network names, and
   ``original_interface`` is used to preserve the interface name.
 
 :Known-Limitations/Considerations/Requirements:
 
-Before enabling this feature, the implications must be discussed with the 
+Before enabling this feature, the implications must be discussed with the
 customer. The following are key considerations for that conversation:
 
 * Only network names defined within kayobe are within scope.
 * Tenant network interfaces, including SR-IOV are not considered or modified.
-* In the case of bonded interfaces, only the bond itself is relablled. 
-  The bond members are displayed with their standard naming.
+* Only the interface directly attributed to a network will be relabelled.
+  This may be a bond, a vlan tagged sub-interface, or both.
+  The parent bond, or bond members are not relabelled unless they are
+  captured within a distinct defined network.
 * Modified entries will be within existing labels. This may be breaking for
   anything that expects the original structure, including custom dashboards,
-  alerting, billing, etc. 
+  alerting, billing, etc.
 * After applying, there will be inconsistency in the time-series db for the
   duration of the retention period i.e until previously ingested entries
   expire.