Manu Garg
Ack. IIRC, even with bigquery surfacer, each metric goes to a different row. But having the single timestamp will allow you to group-by more easily.
@conallob [examples/extensions/myprober/myprober.go](https://github.com/cloudprober/cloudprober/blob/main/examples/extensions/myprober/myprober.go) is not really supposed to mirror the main binary. It should compile and work though. And, it does that: ``` go run ./examples/extensions/myprober/. Registering probe type time=2025-08-06T18:15:50.881-07:00 level=WARN...
Looks like it was on Windows. For windows we upload binaries to pypi: https://pypi.org/project/pacparser/#files Which python version and platform it was?
If it as python 3.13, https://github.com/manugarg/pacparser/pull/221 should take care of it.
@QuAzI Added python 3.14 as well. Can you please retry.
Sorry I didn't follow from your response. Does `pip install` work now?
Let's file another issue for that. Though I think in your case problem is in the alert statement, and reference to variables in template style. I don't believe JS interpreter...
> Including such a field would enable measuring success and failure latencies separately. You can already do that right? There is a `resp_code` metric that HTTP probes export separately. There...
Hi @therealak12 I missed your last question earlier. Sorry to disappoint, but I think it doesn't makes sense to change Cloudprober metrics just for this particular use case. It will...
What we can do here is to provide an option to not capture external probe process's stderr. That way external probe can log directly, retaining the log structure.