github-actions
blackbox_exporter
github-actions | blackbox_exporter | |
---|---|---|
7 | 47 | |
1,667 | 4,306 | |
0.7% | 1.5% | |
6.6 | 8.3 | |
about 1 month ago | 7 days ago | |
TypeScript | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
github-actions
- On April 4, 2022 GitHub Action will force you to use "main" instead of "master" branch
-
On 2022-04-05, the default branch will be renamed from “master” to “main”
Aha: it's because the project team merged this change that intentionally fails the build when people have pinned their workflows to use the deprecated branch name: https://github.com/google-github-actions/setup-gcloud/pull/5...
(that makes sense; there has been a warning in place for a long time, and pinning to a name can be risky when the content within that reference may change over time)
-
Learning Journal 2: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 1)
In the process of finding the answer, I discovered that the small actions are pretty much open-source. I can also go directly to their respective code repositories and learn about them. To run gsutil, I will need a setup-gcloud action.
-
Build an Uptime Monitoring System in Ruby with GCE, Cloud Storage, and PubSub
Like many aspects of the cloud, there are many ways to achieve the same result, but modern software engineering encourages CI/CD processes for several good reasons. As such, we will focus on deploying our service from Github Actions using setup-gcloud
- How to deploy Cloud Functions with GitHub Actions
-
GitOps on Kubernetes - The easy way
GKE_SA_KEY: The service account used for the project with the Base64 encoded JSON service account key. More info available here
blackbox_exporter
-
How I would automate monitoring DNS queries in basic Prometheus
https://github.com/prometheus/blackbox_exporter/blob/master/...
So you need 2 modules, one for each ip version. As for autamating setting these up, we deploy our Prometheus server with salt so we can use Jinja templating in all our Prometheus config files. That really cuts down on repeating boiler plate code.
This is also interesting for other reasons; in host downtime situations you can sometime see they will drop one type of traffic and not the other.
-
Raspberry Pi Remote Server Monitoring over Wifi: Micropython code to monitor tcp port using usocket
A Pi is more than enough to run a full monitoring stack. Why reinvent the wheel?
- Service for monitoring your external IP adresses from a file.
-
Uplink Monitor - Internal IP's to External Facing Status Page
You can also use the blackbox_exporter to probe various endpoints. But in reality, you don't need to do this most of the time since the up metric gets you what you want.
-
Server down detector
Synthetic Monitoring is the Grafana Cloud implementation. It uses the blackbox_exporter
-
how do I start to build an uptime monitoring system such as UptimeRobot or OnlineOrNot?
Prometheus blackbox_exporter. Free and open source.
-
alert for self sign certs
Check something called blackboxexporter https://github.com/prometheus/blackbox_exporter
-
Use prometheus+grafana for bug bounty / pentesting data collection
I have seen some people doing with these traditional relational databases, and I was wondering if it could be a good fit for prometheus+grafana as I have been messing around with prometheus BlackBox exporter (https://github.com/prometheus/blackbox_exporter) for web status monitoring.
-
Prometheus Monitoring Checklist
You should look into the projects https://github.com/prometheus/node_exporter and https://github.com/prometheus/blackbox_exporter
-
Uptime monitoring (~1000 urls)
You could use prometheus as a monitoring tool, blackbox_exporter to "export" the urls to prometheus, alertmanager for notifications, and grafana for nice gui dashboards (and maybe also notifications).
What are some alternatives?
wait-for-jobs - Wait for the specified jobs in the same run to be complete successfully before proceeding, helpful to prestart the job
cloudprober - [Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do.
devops-toolkit
ping_exporter - Prometheus exporter for ICMP echo requests using https://github.com/digineo/go-ping
deploy-appengine - A GitHub Action that deploys source code to Google App Engine.
ssh_exporter
flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
rubygems - Library packaging and distribution for Ruby.
Telegraf - The plugin-driven server agent for collecting & reporting metrics.
actions-cloud-functions
smokeping_prober - Prometheus style smokeping