file_targets for probe options about cloudprober

[manugarg]

This should work. @xenofree, is it not working?

[xenofree]

This is not working.

For query type I have this kind of issue.

  dns_probe {
    query_type: @target.label.query_type@
    resolved_domain: "@target.label.resolved_domain@"
  }

Error initializing cloudprober. Err: line 67: unexpected byte 0x40

  dns_probe {
    query_type: "@target.label.query_type@"
    resolved_domain: "@target.label.resolved_domain@"
  }

Err: line 67: invalid enum: "@target.label.query_type@"

And resolved_domain don't seems to be evaluated.

error in response ;; opcode: QUERY, status: NXDOMAIN, id: 61782
;; QUESTION SECTION:
;\@target.label.resolved_domain\@.      IN       A

[manugarg]

Oops. Sorry, I was wrong. I missed that you were using labels in the probe config. This will not work.

It's going to be hard to implement a generic label replacement mechanism.

The way it works in HTTP probe is:

• If "relative_url" or "host" is not defined in the probe config, and target has these labels, it automatically uses these labels.

We can do something similar for DNS probe.

[manugarg]

@xenofree Please see the announcement here: #679. Active development of this repository is moving to github.com/cloudprober/cloudprober. Unfortunately, we'll have to close all the issues here, and file them again. Can you please do that. Thanks!

[manugarg]

Moved here: cloudprober/cloudprober#26.