Manu Garg

@agora9 Wondering if you got a chance to look at my previous message.

I've not been able to reproduce this bug. We recently released a new version of Cloudprober, v0.11.8, which will have the latest certificates. Would you like to try with that?...

Also copying @mweirauch's comment from https://github.com/google/cloudprober/issues/123#issuecomment-554340102: > I can't yet contribute to how I use Cloudprober, but as the discussion is centering around discovery: > How about support for the...

@tklovett added: Ditto on this. It would also be nice to have some community sanity-checking on what to monitor and how to monitor it accurately. I'll start! ### Overview ####...

@DazWilkin's comment: > Having been initially drawn to deploying Cloudprober (as a container) on Kubernetes, I propose we consider a model in which external probes are (also) deployed as containers....

Other interesting options: - We can fetch Python, Go, Shell code from Github (git-sync) as well, and then run that code through local Python interpreter, Go compiler, and Shell interpreter...

We can implement this through validators: https://cloudprober.org/how-to/validators/

You can use context.Background() as the first argument to robinhood.Dial.

This is the logic this function uses: https://github.com/manugarg/pacparser/blob/536b93b4f475cd91aeb3ff31da6ff7a73fef1baf/src/pacparser.c#L117 Given that pacparser is used by so many people and possibly in many environments, and nothing has changed in the DNS resolve...

_From [[email protected]](https://code.google.com/u/104457145109351650465/) on March 12, 2011 12:23:03_ (No comment was entered for this change.) **Labels:** -Type-Defect -Priority-Medium Type-Enhancement Priority-Low OpSys-Windows