|
|
|
|
|
by atombender
3626 days ago
|
|
Any plans on more native support for Kubernetes? The relabeling spaghetti config you end up with is very confusing and unreadable. Granted, you don't need to touch this confirmation very often, but anyone who's going to operate the cluster will need to understand it thoroughly. The fact that it's ad-hoc (prometheus.io/probe etc. aren't built in) means everyone's config is probably going to be unique and not portable. For example, we found the current config example to be insufficient, since blackbox-exporter needs information about whether its endpoint is HTTP or HTTPS. Kubernetes' template system, combined with variable expansion, seems like it would be a better model for what you're currently trying to do with service discovery. Also: I'm setting this up right now, but it seems there's no exporter for the Kubernetes API proper, just Kubelet? |
|