Max Targets on ping probes

[Nick Zurku]

Hello,

We're seemingly hitting a max targets of "20" on the ping probe, causing all the other ping targets to be discarded. Looking through the documentation and code I'm not seeing where the maxTargets is configurable like it is on the UDP probe.

Is there something I am missing that is unique to the ping probe?

[Manu Garg]

@nzurku There is no limit on how many targets there can be for ping probes (or any probe for that matter).

But, there is a limit on how many targets do you see on the status page and that limit is 20:
https://cloudprober.org/docs/config/surfacer/#cloudprober_surfacer_probestatus_SurfacerConf

You should see all targets on the /metrics page (prometheus exporter page).

You can change the status page's max target limit by adding the following to your config:

surfacer {
  type: PROBESTATUS
   probestatus_surfacer {
      max_targets_per_probe: 100
   }
}

That explicitly configures the probestatus surfacer.

[Nick Zurku]

Thanks, I had misread what the error message was:

time=2023-09-11T18:46:40.794Z level=WARN source=surfacers/internal/probestatus/probestatus.go:241 msg="Reached the per-probe timeseries capacity (20) with target \"HKG1\". All new targets will be silently dropped." system=cloudprober surfacer=probestatus

Looking now, I see why that is specific to the surfacer. Thank you!