-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heatmap is empty for all hosts #100
Comments
See the
|
I'm seeing the same issue, it doesn't seem like adding a source matters here. I'm using docker and the following yaml. targets:
- hosts:
- 8.8.8.8
- 1.1.1.1
interval: 1s # Duration, Default 1s.
network: ip4 # One of ip, ip4, ip6. Default: ip (automatic IPv4/IPv6)
protocol: icmp # One of icmp, udp. Default: icmp (Requires privileged operation)
size: 56 # Packet data size in bytes. Default 56 (Range: 24 - 65535)
# source: # Souce IP address to use. Default: None (automatic selection) Prometheus grabbing metrics:
I'm not sure what is wrong the query for the heatmap based on this info. |
Did you try to use the dashboard.json from this repository? The heatmap query looks like this. I modified it a little bit but the original from repository works and this one, too. sum(rate(smokeping_response_duration_seconds_bucket{host=~"$target"}[1m])) by (le) the rate is [1m] so you need to scrape the smokeping_prober at least every 30s from prometheus to get results. |
@Nachtfalkeaw, yep that's the one. Neither your query nor the original works for me at least. Pings are at 1s interval, switched to 15s just for fun and it is the same as expected. |
it works if it's 2m instead of 1m, not sure why... what am I missing |
My scrape interval was too low in prometheus (as you mentioned) (new to prometheus) |
I just meet the same promble while try to start smokeping_prober by nologin user. Run it by root ok |
The Packet Loss and Latency charts plot fine.
Screenshot: https://imgur.com/a/QlZJCnS
Invoked via systemd as:
Also tried with:
Logs show no error:
Config:
System info:
The text was updated successfully, but these errors were encountered: