spec
blackbox_exporter
Our great sponsors
| spec | blackbox_exporter | |
|---|---|---|
| 31 | 47 | |
| 4,756 | 4,279 | |
| 2.9% | 2.3% | |
| 7.5 | 8.2 | |
| 15 days ago | 11 days ago | |
| Python | 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.
spec
-
Data Streaming Architecture
The structure of this example message is using CloudEvents specification:
- CloudEvents Event Specification
-
Microsoft Azure Event Grid MQTT Protocol Support and Pull Message Delivery Are Now in Public Preview
Microsoft has expanded the Event Grid capabilities to enhance system interoperability by introducing support for MQTT v3.1.1 and v5.0 protocols. This allows customers to publish and subscribe to messages for Internet of Things (IoT) solutions. This new support, currently available in public preview, complements the existing support for CloudEvents 1.0.
-
OpenTelemetry for Open Source Telemetry?
You are looking for https://cloudevents.io/ . That is what you should use if you plan to do homegrown. I would however recommend you to use use segment + amplitude, juno, mixpanel . If you are early these are mostly free up to a point.
- FLaNK Stack Weekly 27 March 2023
-
Format of a Kafka message envelope
When modeling an event in a streaming application, what "meta" fields to you use? Like timestampts, versions, some context etc... I think there are some efforts to introduce a standard format like Cloud Events but wondering if you guys have any different suggestions?
-
Show HN: Automatisch – open-source workflow automation, an alternative to Zapier
CloudEvents is trying to standardize on the messaging
- FLiP Stack Weekly for 21 Jan 2023
- cloudevents: A specification for describing event data in a common way
-
A message queue focus on serverless program
Hello guys, actually, vanus can directly deliver messages to OpenFaaS without this kind of connector. Because vanus can deliver messages that follow the CloudEvents standard, OpenFaaS can also receive such messages. More details https://docs.linkall.com/how-to/use-gcloud-functions
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?
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
cloudprober - [Moved to cloudprober/cloudprober] An active monitoring software to detect failures before your customers do.
asyncapi-to-postman - Creates a Postman collection from an AsyncAPI file.
ping_exporter - Prometheus exporter for ICMP echo requests using https://github.com/digineo/go-ping
cupid - A library that focuses on finding and analyzing the relationships between AsyncAPI documents. It outputs a map of the system architecture. Except for a default map, it is possible to get output as mermaid.js flow diagram, PlantUML class diagram and more to come.
ssh_exporter
youtube-websub-subscription-handler - This is a WebSub subscription handler for YouTube video feed update | YouTube 비디오 피드 업데이트를 WebSub 기능을 이용해 받아 처리합니다
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
generator - Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
Telegraf - The plugin-driven server agent for collecting & reporting metrics.
PowerPlatformConnectors - This is a repository for Microsoft Power Automate, Power Apps, and Azure Logic Apps connectors
smokeping_prober - Prometheus style smokeping