David Leadbeater

The underlying reason here is actually very similar to #10257, pods are kept around after termination; this is dependent on kube-controller-manager GC flags and the amount of pod churn in...

Note I disclosed this in advance to libera.chat and they have implemented network side filtering, so it's worth mentioning it is possible to filter this at the server side too.

The main point I'd be interested in feedback on is the interface; I've used the labels that were there already. The other option is adding something like the `extensions` pattern...

Given blackbox_exporter is stateless, it is hard for it to keep a count of anything, could you expand a bit on what you had in mind? I think some of...

> Ah good point, you mean that blackbox-exporter doesn't have a metrics registry? If that's the case, any known problems > that prevent us from adding a registry? There is...

It was mentioned in #799 -- it would be nice, but per https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-6 there's quite a few possibilities, maybe we could pick the ones we think are likely... Say NOERROR,...

Adding some reviewers to get any thoughts on labels vs numbers...

blackbox_exporter doesn't have any built-in DNS cache, it's not its place to do that. The standard Unix way to do this is to have some caching done out of process,...

`check rules` is designed for Prometheus rules. I think you’ve provided either a Prometheus config or an alertmanager config. Those need either `promtool check config` or `amtool check-config`.

WASI on top of WASM is the common system level interface, however it does not currently [support mmap](https://github.com/bytecodealliance/wasmtime/blob/main/docs/WASI-rationale.md#why-no-mmap-and-friends) -- mmap is pretty crucial for Prometheus (although it could be worked...