Closed niyaodong closed 1 year ago
I found that issue 2 is solved if I delelte "keep_last_value" on panel Metrics browser setting.
sort(keep_last_value(avg_over_time(mtr_rtt_seconds{host=~"$station",name=~"$name_mtr", type="mean"}[$__interval])))
This is the explanation of “keep_last_value”,but I don't know the difference if I delete it.
keep_last_value(q) fills gaps with the value of the last non-empty point in every time series returned by q.
old
Hi syepes,
It's me again...
I'm looking forward to deploying network_exporter in the production env as my leader was very satisfied with the monitoring stack. But I found something I am not able to deal with. so that I post it here.
It's not an issue. I would like to sort the items by ttl. I looked up a lot of information but couldn't find a way to do it.
Even if the node is unreachable, the panel still shows it. In the time range shown below, hops 3-7 areunreachable, but they keep the same value like a straight line until they became reachable. this issue is not relevant to network_exporter as I checked network_exporter metircs were OK. Could it be caused by Victoriametrics?
Invalid nodes will still be displayed. As the panel shown below, we can see the hop 11 keeps updating. As I understand, currently the hop 11 should be "unknown" as the MTR shown below.