Marcelo Magallon

> Adding some reviewers to get any thoughts on labels vs numbers... Sorry, I was sure I had replied to this... I would prefer @SuperQ's proposal. That makes it easier...

Sorry, I looked at this the other day and forgot to follow up... where's the 120s coming from?

> Sorry, I looked at this the other day and forgot to follow up... > > where's the 120s coming from? Ah, the builtin default. Sorry, I missed that.

@SuperQ I think the question is still valid as a bug report. Starting here: ``` ts=2021-02-23T06:19:22.251254881Z caller=main.go:304 module=http_2xx target="https://mycompany.com/?debug=true" level=info msg="Beginning probe" probe=http timeout_seconds=119.5 ``` that 119.5 is the timeout...

@devops-42 where you able to fix this issue? I was just trying to reproduce with the provided Dockerfile, but that fails. After fixing it, it fails in a different way...

If I understand correctly what you are trying to do @zloidemon, you could achieve that with relabelling. My guess is that you have something like: ``` probe_success{instance="https://google.com:9999/blah", job="blackbox"} probe_success{instance="google.com", job="blackbox"}...

I see... The "UP" value in the state column refers to the Prometheus scrape target, not the target of the blackbox module (the next column). From the Prometheus docs: >...

> Apologies for not including unit tests with this. I took a look at the tests and since the TLS tests are around self signed CA, I'm not sure how...

@bgagnon any responses to Brian's most recent comment?

> We could provide a list of default "always expodsed" rcodes as a command line flag. Something like `--probe.dns.rcodes=NOERROR,SRVFAIL,NXDOMAIN"`. If the rcode is some other code, we could either assign...