Open arsbest opened 5 months ago
I'm also seeing this behavior with mtr targets. Something is preventing path from being stored for a number of hops, resulting in most data points being associated with unknown.
I've confirmed that running mtr to the same target manually from within the network_exporter container results in the expected hop values/ips. Wish I had more insight as to where exactly it might be encountering issues. Happy to set flags/logging etc if it would help narrow down! My data is pretty similar as well:
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="11", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="12", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="13", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="14", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="15", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="3", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="4", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="5", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="6", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="7", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="8", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="unknown", target="204.2.29.8", ttl="9", type="best"}
0
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="10.10.10.1", target="204.2.29.8", ttl="2", type="csd"}
0.000036422
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="192.168.160.1", target="204.2.29.8", ttl="1", type="csd"}
0.000020767
mtr_rtt_seconds{host="network_exporter", instance="network_exporter:9427", job="vm_network_exporter", name="target_1", path="204.2.29.8", target="204.2.29.8", ttl="16", type="csd"}
I use network_exporer v1.7.6. For example try to probe mtr
google.com
. And i cant see in metric addresses of intermediate hops. If i correctly understand this info must be inpath
labelIf I run local
mtr google.com
i can see host ip for each hop.