My proposal for this issue and for others that will not be managed by operator is to accept a job append configuration. There is still work to be done to have a first class support for blackbox probing. Below are the prometheus spec and the job configmap. SMTP/Maildir MDA blackbox prober; SoftEther exporter; SSH exporter; Teamspeak3 exporter; Transmission exporter; Unbound exporter; WireGuard exporter; Xen exporter; When implementing a new Prometheus exporter, please follow the guidelines on writing exporters Please also consider consulting the development mailing list. Bit is it possible to add custom job config for specifi service monitor? Another solution is to use Probe CRD. We'll eventually have to figure out a meaningful abstraction to use it, but we're not there yet. Which means we would be deploying a dead resource. Blackbox exporter can be deployed by the following command. I believe that the integration will look something like the integration of the Alertmanager in the Prometheus object, where we loosely reference a blackbox exporter running behind a specific Service, and then an abstracted form of blackbox probing configuration in a ServiceMonitor. @grrywlsn actually in that case what you want to do is create an Endpoints object yourself. Menu Close menu. If anything is not as clear as it should be we're happy about PRs! As a system administrator, or as an application developer, you are often issuing ping commands in order to check the availability of your services.. You may want to check your website uptime, if your website is accessible and if it is loading fast for your users. The blackbox exporter doesn't have any state of its own, so a StatefulSet would be exaggerated, but some kind of abstraction would make sense, however, currently I am thinking of mainly abstracting the way the blackbox exporter is configured, rather than how it is run. The Operator automatically generates Prometheus scrape configuration based on the definition. We want to build abstractions that are higher up, so people don't need to know the Prometheus/blackbox exporter configuration paradigms. After installing the generated manifests, you can create Probe resources, for example: 'kube-prometheus/kube-prometheus.libsonnet', // serviceMonitor is separated so that it can be created after the CRDs are ready, blackbox-exporter.monitoring.svc.cluster.local:19115. As this is a common theme for etcd, we've prepared an example for it: https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/manifests/etcd/etcd-bootkube-gce.yaml. I'm not sure I understand the question. Hopefully soon coming to your prometheus-operator deployments! The configuration section lists the parameters that can be configured during installation. I'm working on moving our Prometheus deployments to Prometheus Operator deployments at the moment, so would be happy to update when we've got something good. Read more. Prometheus Blackbox-Exporter – monitoring TLS certificates. set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues and prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues to false. During my last project, we decided to use Prometheus Operator as our monitoring and alerting tool. By multi-target exporterpattern we refer to a specific design, in which: 1. the exporter will get the target’s metrics via a network protocol. Configuring Blackbox exporter timeouts . I configured the Service Monitor, deployment, working by prometheus operator. How about making this into a ThirdPartyResource named ExternalService? Additionally, if we add blackbox_exporter to be deployed by prometheus-operator, there are zero guarantees any data will be gathered as external probe targets need to be first defined by the user. https://github.com/prometheus/blackbox_exporter#prometheus-configuration, https://github.com/coreos/prometheus-operator/blob/master/contrib/kube-prometheus/manifests/etcd/etcd-bootkube-gce.yaml, https://github.com/coreos/prometheus-operator/blob/master/Documentation/custom-configuration.md. Note for the Probe CRD: Probe, which declaratively specifies how groups of ingresses or static targets should be monitored. prometheus/blackbox_exporter#113. For example performing real HTTP requests on your application to see whether it is responding the way you expect. Prometheus Blackbox Exporter By llama-charmers Monitoring; stable 7 juju deploy cs:prometheus-blackbox-exporter. #2832 is working on this API. I struggled figuring out how to get this working too. The appendJobSelector will be attached to the end of the job configuration, generated by prometheus. Stack Overflow | The World’s Largest Online Community for Developers I'd like to help out with some docs around this as it wasn't very clear. Suggestions are welcomed, https://github.com/gianrubio/prometheus-operator/tree/blackbox-exporter/Documentation/proposals/blackbox-exporter#generated-prometheus-config. I have configured a blackbox exporter for monitoring some urls using prometheus. You signed in with another tab or window. We are happy to give advice on how to make your exporter as useful and … For a deeper integration, we have to understand the different use cases better. The Prometheus collect the metrics but I cannot tell them apart. There have been issues around this in the past so if you can get around to writing this doc, that would be amazing! it wasn't all that obvious from the docs that I could see. I ended up with a Deployment (and Service) exposing blackbox_exporter and then configuring prometheus to scrape via blackbox_exporter's /probe endpoint.