![]() ![]() imap_starttls and smtp_starttls both make IMAP and SMTP connections, respectively, over TLS. This does what you’d expect - checking the response of an HTTP request for a 2XX response code. For testing HTTP(s) targets I’ve defined an http_2xx module. The modules in the configuration above define what sort of blackbox testing the blackbox_exporter can perform. port: 9115 protocol: TCP targetPort: 9115 selector: ![]() mountPath: /etc/blackbox_exporter name: blackbox-exporter volumes:ĭefaultMode: 420 name: blackbox-exporter name: blackbox-exporter. image: prom/blackbox-exporter:v0.22.0 name: blackbox-exporter securit圜ontext: Name: blackbox-exporter namespace: prometheus data:ĪpiVersion: apps/v1 kind: Deployment metadata:Īpp: blackbox-exporter name: blackbox-exporter namespace: prometheus spec: To deploy blackbox_exporter on Kubernetes I used the following manifest: At the time I had no experience with Prometheus, and since everyone was talking about it at the time, I figured it was time to learn. However, I never quite got it working the way I wanted. I stumbled across Cloudprober and tried to get it working with Stackdriver. I wanted to check service health of TCP services (i.e. Also, the TCP checks are rather limited, simply confirming that a connection could be made. However, at the time, uptime checks did not check for SSL certificate expiration, something I considered important given I was using 90 day Let’s Encrypt certificates and wanted to ensure that certificate rotation was working as expected. Google Cloud Monitoring has support for uptime checks which can be used to perform blackbox monitoring of HTTP, HTTPS, and TCP services. Since I was already running some infrastructure on Google Cloud Platform, I first took a look at Stackdriver (now Google Cloud Monitoring). I surveyed the hosted service landscape but the available free options didn’t support the variety of services I needed to monitor and the paid services cost as much as a single VPS at ARP Networks. I had quite a few services to monitor, including multiple Web servers, a mail server, IRC server, and more. I had used Pingdom for this in the past, but they killed their free plan in 2019. A couple of years ago I was looking for a way to monitor the health of various services I had deployed across virtual machines and containers running on my home network. Prior to migrating from Cacti to Prometheus for infrastructure monitoring, I’d already been using Prometheus for blackbox monitoring. ![]()
0 Comments
Leave a Reply. |