Bug 1433734 - Strange statsd nic metrics
Summary: Strange statsd nic metrics
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Services
Version: 4.20.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.3
: 4.19.16
Assignee: Yaniv Bronhaim
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-19 15:19 UTC by Yaniv Bronhaim
Modified: 2017-07-06 13:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-06 13:09:24 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 74417 0 master MERGED vdsm metrics: replace dots with underscore in entity names 2017-04-25 17:18:46 UTC
oVirt gerrit 75998 0 ovirt-4.1 MERGED vdsm metrics: replace dots with underscore in entity names 2017-05-23 09:11:25 UTC

Description Yaniv Bronhaim 2017-03-19 15:19:29 UTC 
Description of problem:
In fluentd we receive strange nic metrics format to statsd plugin:
nic_183
nic_182

The actual nics' names are enp4s0f1.183 and enp4s0f1.182
So looks like vdsm ignores the string before the dot

Expected result should be 

hosts.nic.VLAN183.tx
hosts.nic.VLAN183.tx_dropped

hosts.nic.enp4s0f1_182.tx
hosts.nic.enp4s0f1_182.tx_dropped

dots in nic or volume name should be dropped or changed to underscore

Version-Release number of selected component (if applicable):
4.20

How reproducible:
always
Comment 4 Lukas Svaty 2017-06-05 16:56:31 UTC 
verified in ovirt-engine-metrics-1.0.3-1.el7ev.noarch

"_source": {
    "collectd": {
      "interface": {
        "if_errors": {
          "rx": null,
          "tx": null
        }
      },
      "plugin": "interface",
      "interval": 10,
      "type": "if_errors",
      "type_instance": "",
      "dstypes": "derive",
      "plugin_instance": "eth0.test"
    },
Note You need to log in before you can comment on or make changes to this bug.