unbound-docker-rpi
Grafana
unbound-docker-rpi | Grafana | |
---|---|---|
6 | 380 | |
133 | 60,503 | |
- | 0.8% | |
5.4 | 10.0 | |
about 2 months ago | 2 days ago | |
Shell | TypeScript | |
MIT License | GNU Affero General Public License v3.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.
Grafana
- Grafana: From Dashboards to Centralized Observability
-
Docker Log Observability: Analyzing Container Logs in HashiCorp Nomad with Vector, Loki, and Grafana
Monitoring application logs is a crucial aspect of the software development and deployment lifecycle. In this post, we'll delve into the process of observing logs generated by Docker container applications operating within HashiCorp Nomad. With the aid of Grafana, Vector, and Loki, we'll explore effective strategies for log analysis and visualization, enhancing visibility and troubleshooting capabilities within your Nomad environment.
-
Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
To help us visualize these scenarios, we'll build a Grafana Dashboard so we can follow along.
-
Monitoring, Observability, and Telemetry Explained
Visualization and Analysis: Choose a tool with intuitive and customizable dashboards, charts, and visualizations. A question to ask is, "Are the visualization features of this tool user-friendly and adaptable to our team's specific needs?" Tools like Grafana and Kibana provide powerful visualization capabilities.
-
4 facets of API monitoring you should implement
Prometheus: Open-source monitoring system. Often used together with Grafana.
- Grafana: Open and composable observability and data visualization platform
-
The Mechanics of Silicon Valley Pump and Dump Schemes
Grafana
-
Reverse engineering the Grafana API to get the data from a dashboard
Yes I'm aware that Grafana is open source but the method I used to find the API endpoints is far quicker than digging through hundreds of files in a codebase I'm not familiar with.
-
Building an Observability Stack with Docker
So, you will add one last container to allow us to visualize this data: Grafana, an open-source analytics and visualization platform that allows us to see traces and metrics simply. You can set Grafana to read data from both Tempo and Prometheus by setting them as datastores with the following grafana.datasource.yaml config file:
-
How to collect metrics from node.js applications in PM2 with exporting to Prometheus
In example above, we use 2 additional parameters: code (HTTP response code) and page (page identifier), which provide detailed statistics. For example, you can build such graphs in Grafana:
What are some alternatives?
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
Thingsboard - Open-source IoT Platform - Device management, data collection, processing and visualization.
gravity-sync - 💫 The easy way to synchronize the DNS configuration of two Pi-hole 5.x instances.
Apache Superset - Apache Superset is a Data Visualization and Data Exploration Platform [Moved to: https://github.com/apache/superset]
unbound-docker - Unbound DNS Server Docker Image
Heimdall - An Application dashboard and launcher
Pi-hole - A black hole for Internet advertisements
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
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.
Thingspeak - ThingSpeak is an open source “Internet of Things” application and API to store and retrieve data from things using HTTP over the Internet or via a Local Area Network. With ThingSpeak, you can create sensor logging applications, location tracking applications, and a social network of things with status updates.
unbound-config - fragmented configuration files for unbound recursive dns resolver
uptime-kuma - A fancy self-hosted monitoring tool