Skip to content
Branch: master
Find file History
manugarg Add support for adding additional labels to probe results.
This change adds support for adding additional labels to probe results. Additional labels can either be static (you specify label value in the config itself) or can be target based in which case label values come from the target labels.

Example probe config:

probe {
  ..
  additional_label {
    key: "src_zone"
    value: {{.zone}} # Will expand to current zone at the time of config parsing.
  }
  additional_label{
    key: "dst_zone"
    value: "target.labels.zone"
  }
}

Let's say we are probing two targets: target1 (no zone label), target2 (has zone label). Our metrics will look like the following:

total{ptype=http, probe=probe1, dst=target1, src_zone=us-central1-a, dst_zone=""} 34
total{ptype=http, probe=probe1, dst=target2, src_zone=us-central1-a, dst_zone="us-central1-b"} 54

PiperOrigin-RevId: 268986659
Latest commit e0bd453 Sep 13, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
cmd Move protos to their own packages. Apr 12, 2018
proto Update protobufs' Go code. Jul 23, 2019
http.go Add support for adding additional labels to probe results. Sep 14, 2019
http_test.cfg
http_test.go Add support for adding additional labels to probe results. Sep 14, 2019
request.go Move IP version (ip_version) option to probe level. May 31, 2019
You can’t perform that action at this time.