Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1546198 - [RFE] ovs-stats metrics list to add to collectd
[RFE] ovs-stats metrics list to add to collectd
Status: ASSIGNED
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch (Show other bugs)
10.0 (Newton)
Unspecified Unspecified
medium Severity medium
: ---
: 10.0 (Newton)
Assigned To: Matteo Croce
Leonid Natapov
: FutureFeature, Reopened, Triaged, ZStream
Depends On:
Blocks: 1544767
  Show dependency treegraph
 
Reported: 2018-02-16 09:57 EST by Matthias Runge
Modified: 2018-10-29 08:51 EDT (History)
20 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1544767
Environment:
Last Closed: 2018-06-27 19:33:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2102 None None None 2018-06-27 19:35 EDT

  None (edit)
Comment 6 errata-xmlrpc 2018-06-27 19:33:21 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2102
Comment 8 Matthias Runge 2018-07-18 06:36:16 EDT
ovs upstream commit https://github.com/openvswitch/ovs/commit/971f4b394c6e8480300494787fe919869ff3886c
Comment 9 Matthias Runge 2018-08-27 03:08:52 EDT
After being able to test this with the collectd change, I still can not see some of the requested metrics:

For example, I'm getting (and the same via ovs-ofctl -O OpenFlow14 dump-ports br-admin)

Either, we are missing something here, or it has not been implemented?

overcloud-compute-0/ovs_stats-br-admin.br-admin/if_collisions
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_dropped
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_errors
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_packets
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_rx_errors-crc
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_rx_errors-frame
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_rx_errors-over
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_rx_octets
overcloud-compute-0/ovs_stats-br-admin.br-admin/if_tx_octets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_dropped
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_errors
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-128_to_255_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-1523_to_max_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-1_to_64_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-256_to_511_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-512_to_1023_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-65_to_127_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_packets-broadcast_packets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_errors-crc
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_errors-rx_fragmented_errors
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_errors-rx_jabber_errors
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_errors-rx_oversize_errors
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_errors-rx_undersized_errors
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_rx_octets
overcloud-compute-0/ovs_stats-br-admin.dpdk0/if_tx_octets
overcloud-compute-0/ovs_stats-br-admin.phy-br-admin/if_packets
overcloud-compute-0/ovs_stats-br-admin.phy-br-admin/if_rx_octets
overcloud-compute-0/ovs_stats-br-admin.phy-br-admin/if_tx_octets
Comment 10 Matteo Croce 2018-10-12 18:05:36 EDT
Hi Matthias,

I made a setup with OVS 2.10 and collectd 5.8.0 with the ovs_stats plugin.
I understand that there is request to collect some statistics, but I've found that many are already present.

These are the requested members

- rx_mbuf_allocation_errors
- rx_undersize_errors
- rx_error_bytes
- rx_good_bytes
- rx_total_bytes
- rx_good_packets
- rx_management_packets
- rx_multicast_packets
- rx_total_missed_packets
- rx_total_packets
- rx_l3_l4_xsum_error
- rx_management_dropped
- tx_good_bytes
- tx_q0_bytes
- tx_broadcast_packets
- tx_good_packets
- tx_management_packets
- tx_total_packets

and these are the already present elements.

# collectdctl listval |grep -o '/.*ovs.*$'
/interface-ovs-netdev/if_dropped
/interface-ovs-netdev/if_errors
/interface-ovs-netdev/if_octets
/interface-ovs-netdev/if_packets
/interface-ovsbr0/if_dropped
/interface-ovsbr0/if_errors
/interface-ovsbr0/if_octets
/interface-ovsbr0/if_packets
/ovs_stats-ovsbr0.guest1/if_dropped
/ovs_stats-ovsbr0.guest1/if_packets
/ovs_stats-ovsbr0.guest1/if_rx_octets
/ovs_stats-ovsbr0.guest1/if_tx_octets
/ovs_stats-ovsbr0.guest2/if_dropped
/ovs_stats-ovsbr0.guest2/if_packets
/ovs_stats-ovsbr0.guest2/if_rx_octets
/ovs_stats-ovsbr0.guest2/if_tx_octets
/ovs_stats-ovsbr0.ovsbr0/if_collisions
/ovs_stats-ovsbr0.ovsbr0/if_dropped
/ovs_stats-ovsbr0.ovsbr0/if_errors
/ovs_stats-ovsbr0.ovsbr0/if_packets
/ovs_stats-ovsbr0.ovsbr0/if_rx_errors-crc
/ovs_stats-ovsbr0.ovsbr0/if_rx_errors-frame
/ovs_stats-ovsbr0.ovsbr0/if_rx_errors-over
/ovs_stats-ovsbr0.ovsbr0/if_rx_octets
/ovs_stats-ovsbr0.ovsbr0/if_tx_octets

some info can be gathered by the generic interface plugin, others are missing and I will try to add them.

Note You need to log in before you can comment on or make changes to this bug.