unbound-docker-rpi
alertmanager
unbound-docker-rpi | alertmanager | |
---|---|---|
6 | 13 | |
133 | 6,295 | |
- | 1.0% | |
5.4 | 9.2 | |
about 2 months ago | 4 days ago | |
Shell | Go | |
MIT License | 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.
unbound-docker-rpi
- Pihole, unbound and WireGuard.
-
My Raspberry Pi 4 Dashboard
- Unbound
-
Pi-Hole with Unbound reporting Cloudflare DNS when checking for DNS leaks
In Pi-Hole, all the queries are sent to and answered by the Unbound docker container, as confirmed by the Pi-Hole logs. I am not seeing any query in Pi-Hole going outside my network for resolution, so I am stumped as to what the cause of this is. The best guess that I could come up with is that somehow Unbound got configured in forwarding mode instead of a recursive resolver. I am not an expert on networking or Unbound, so I am looking for anyone who has an idea as to how to solve this. If it helps, I used https://github.com/MatthewVance/unbound-docker-rpi as the docker image to set up unbound.
-
Starting Unbound in a Docker Container
If your using a pi, you need to use the pi image. Also I remember that I created these files before deploying the container: config files for unbound * a-records.conf ```
- How to install Unbound and Pi-hole in Docker using docker-compose
-
Best Docker image to use to install Pi-hole (along with PiVPN and Unbound)?
mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.
alertmanager
-
My Raspberry Pi 4 Dashboard
- Alert Manager
-
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).
-
Alertmanager with SNS Topic
I found this other example below from this repo https://github.com/prometheus/alertmanager/issues/2559, but it is neither working.
-
Ultra Monitoring with Victoria Metrics
vmalert: executes a list of the given alerting or recording rules against configured data sources. For sending alerting notifications vmalert relies on configured Alertmanager. Recording rules results are persisted via remote write protocol. vmalert is heavily inspired by Prometheus implementation and aims to be compatible with its syntax
-
Can Prometheus act similar to OPC A&E server?
Yes, I believe you can do all of what you're looking for without a UI. The alertmanager api has the ability to register receivers as well as to poll for alerts, silence them, etc: https://github.com/prometheus/alertmanager/blob/main/api/v2/openapi.yaml
-
Customize Pushovert alerts ?
I found it, unfortunately it doesn't help.
-
Part I: EC2 with Prometheus
#cloud-config # environment: ${environment} runcmd: # install AWS CLI, neeeded for downloading of configuration files - | apt-get update && apt-get install unzip -y curl -Lo awscli.zip https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip unzip awscli.zip ./aws/install rm awscli.zip # install prometheus binary - | curl -Lo prometheus.tar.gz https://github.com/prometheus/prometheus/releases/download/v2.33.1/prometheus-2.33.1.linux-arm64.tar.gz tar -xvf prometheus.tar.gz cp ./prometheus-2.33.1.linux-arm64/prometheus /usr/local/bin/prometheus rm -rf ./prometheus-2.33.1.linux-arm64 rm -rf prometheus.tar.gz # install alertmanager binary - | curl -Lo alertmanager.tar.gz https://github.com/prometheus/alertmanager/releases/download/v0.23.0/alertmanager-0.23.0.linux-arm64.tar.gz tar -xvf alertmanager.tar.gz mv ./alertmanager-0.23.0.linux-arm64/alertmanager /usr/local/bin/alertmanager rm -rf alertmanager-0.23.0.linux-arm64 rm alertmanager.tar.gz # vait for EBS volume - | while [ ! -b $(readlink -f /dev/nvme1n1) ]; do echo "waiting for device /dev/nvme1n1" sleep 5 done # format volume blkid $(readlink -f /dev/nvme1n1) || mkfs -t ext4 $(readlink -f /dev/nvme1n1) # create a mount mkdir -p /data if ! grep "/dev/nvme1n1" /etc/fstab; then echo "/dev/nvme1n1 /data ext4 defaults,discard 0 0" >> /etc/fstab fi # mount volume mount /data # enable and start systemd services - | systemctl daemon-reload systemctl enable prepare-prometheus.service && systemctl start prepare-prometheus.service && sleep 10 systemctl enable prometheus.service && systemctl start prometheus.service systemctl enable alertmanager.service && systemctl start alertmanager.service write_files: - path: /usr/local/bin/prepare-prometheus permissions: '0744' content: | #!/bin/sh mkdir -p /etc/prometheus aws s3 cp s3://${s3_bucket}/prometheus.yaml /etc/prometheus/prometheus.yaml aws s3 cp s3://${s3_bucket}/alertmanager.yaml /etc/prometheus/alertmanager.yaml aws s3 cp s3://${s3_bucket}/prometheus.rules.yaml /etc/prometheus/prometheus.rules.yaml curl -X POST http://localhost:9090/-/reload || true - path: /etc/systemd/system/prepare-prometheus.service content: | [Unit] Description=Prepare prometheus / alertmanager configuration Wants=network-online.target After=network-online.target [Service] Type=oneshot ExecStart=/usr/local/bin/prepare-prometheus # please note data.mount in dependencies - path: /etc/systemd/system/prometheus.service content: | [Unit] Description=Prometheus Wants=network-online.target After=network-online.target data.mount prepare-prometheus.service [Service] Type=simple ExecStart=/usr/local/bin/prometheus \ --config.file /etc/prometheus/prometheus.yaml \ --storage.tsdb.path /data/ \ --web.enable-lifecycle \ --web.console.templates=/etc/prometheus/consoles \ --web.console.libraries=/etc/prometheus/console_libraries \ --enable-feature=remote-write-receiver [Install] WantedBy=multi-user.target - path: /etc/systemd/system/alertmanager.service content: | [Unit] Description=Alert Manager Wants=network-online.target After=network-online.target data.mount prepare-prometheus.service [Service] Type=simple ExecStart=/usr/local/bin/alertmanager \ --config.file /etc/prometheus/alertmanager.yaml \ --storage.path=/data/ [Install] WantedBy=multi-user.target
- Prometheus trigger script on alert
-
Is this a terrible way of getting timezone awareness into my Prometheus alerts?
Prometheus recently added native support for time ranges in the alerting config https://github.com/prometheus/alertmanager/issues/876
-
It took almost a full day, but I finally got a decent homelab diagram :D Feedback is most welcome!
Prometheus)Alertmanager: https://github.com/prometheus/alertmanager | https://prometheus.io/
What are some alternatives?
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
gravity-sync - 💫 The easy way to synchronize the DNS configuration of two Pi-hole 5.x instances.
loki - Like Prometheus, but for logs.
unbound-docker - Unbound DNS Server Docker Image
synology-notifications - Synology notifications service
Pi-hole - A black hole for Internet advertisements
node_exporter - Exporter for machine metrics
cloudblock - Cloudblock deploys secure ad-blocking and VPN for all devices. Text and video guides included! 6 supported cloud providers, plus Ubuntu and Raspberry Pi. Cloudblock deploys Wireguard VPN, Pi-Hole DNS Ad-blocking, and DNS over HTTPS in a cloud provider - or locally - using Terraform and Ansible.
NPushOver - Full fledged, async, .Net Pushover client
unbound-config - fragmented configuration files for unbound recursive dns resolver
rook - Storage Orchestration for Kubernetes