Skip to content
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

inputs.ping native sends wrong number of pings #8501

Closed
bjoe2k4 opened this issue Dec 2, 2020 · 1 comment · Fixed by #8577
Closed

inputs.ping native sends wrong number of pings #8501

bjoe2k4 opened this issue Dec 2, 2020 · 1 comment · Fixed by #8577
Labels
area/ping bug unexpected problem or unintended behavior

Comments

@bjoe2k4
Copy link

bjoe2k4 commented Dec 2, 2020

Relevant telegraf.conf:

[global_tags]
[agent]
  interval = "10s"
  round_interval = true
  metric_batch_size = 1000
  metric_buffer_limit = 10000
  collection_jitter = "0s"
  flush_interval = "10s"
  flush_jitter = "0s"
  precision = ""
  debug = false
  quiet = true
  logtarget = "file"
  logfile = "/var/log/telegraf/telegraf.log"
  logfile_rotation_interval = "1d"
  hostname = ""
  omit_hostname = false
[[outputs.prometheus_client]]
  listen = ":9283"
  metric_version = 2
[[inputs.ping]]
urls = ["vodafone.de" ]
count = 5
method = "native"
ping_interval = 0.2
timeout = 4.0

System info:

RaspberryOS with a 4GB Raspi4
Linux raspi-pihole2 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux
Telegraf 1.16.2 (git: release-1.16 962082f) (offical release)

Steps to reproduce:

  1. Set above config & start telegraf + prometheus
  2. Wait for a day

Expected behavior:

telegraf sends and receives exactly 5 packets every 10s when there is no packetloss.

Actual behavior:

telegraf sometimes seems to send more packages than it is supposed to (6 instead of 5)

telegraf

The question is if the 6th packet is actually sent or if it is just a reporting bug. A 100% correlation with a packetloss of 16.66% rather points to a bug.

Additional info:

@bjoe2k4 bjoe2k4 added the bug unexpected problem or unintended behavior label Dec 2, 2020
@ssoroka ssoroka changed the title inputs.ping native sends wring number of pings inputs.ping native sends wrong number of pings Dec 3, 2020
@reimda
Copy link
Contributor

reimda commented Dec 15, 2020

Do you get the same behavior with ping method = "exec"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ping bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants