LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
    • groundcover MCP
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Issues
    • Role-Based Access Control (RBAC)
    • Service Accounts
    • API Keys
    • APIs
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Querying you data using an API
      • Using KEDA autoscaler with groundcover
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • Incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • Integrating Pi-hole with groundcover
  • Step 1: Enable Custom Metrics
  • Step 2: Import dashboard using Grafana ID
  • That's it!
Export as PDF
  1. Integrations
  2. 3rd-party metrics

Pi-hole

Last updated 1 year ago

Pi-hole is a comprehensive network-wide ad blocking and tracking protection solution, originally designed for Raspberry Pi devices but now widely compatible with various systems. It functions as a DNS sinkhole, intercepting queries for known ad-serving domains and preventing unwanted content from reaching the user's device. This results in a cleaner, faster web browsing experience without the intrusive ads. Beyond just ad blocking, Pi-hole also enhances privacy by blocking trackers that monitor online activity.

What sets Pi-hole apart is its ability to block advertisements and trackers at the network level, meaning it can protect all devices connected to the network without the need for individual ad-blocking software on each device. Its lightweight design ensures it can run seamlessly on low-power devices, making it an efficient solution for improving network performance and security. Pi-hole's user-friendly web interface provides an accessible way for users to monitor network activity, view statistics, and customize their blocking lists, offering a tailored and transparent network management experience.

Integrating Pi-hole with groundcover

To start accessing granular insights, just follow these 2 super easy steps:

Step 1: Enable Custom Metrics

Follow our on how to enable scraping custom metrics on groundcover.

Step 2: Import dashboard using Grafana ID

In the groundcover platform, go to Dashboards -> New -> Import.

In the box titled "Import via grafana.com", enter one of the following dashboard IDs, then click "Load".

ID
Name
Description
More Info

10176

Pi-hole Exporter

This is a Pi-hole dashboard when using the https://github.com/eko/pihole-exporter Prometheus exporter

6603

Pi-hole Statistics

Example Dashboard for statistics gathered from Pi-hole

14475

Pi-hole UI

Watch either a single Pi-hole system or combine the statics of several in a single pane.

13565

Pi-hole - RESTful API

Grafana Dashboard that consumes Pi-hole API without auth. All simple, leveraging the input.http from telegraf.

14283

PI-Hole Exporter

This is a PI-Hole dashboard when using the https://github.com/eko/pihole-exporter Prometheus exporter

That's it!

You can now see the imported dashboard in your list of Dashboards and start using it immediately.

You can repeat this action to load as many of these dashboards as you like.

If you import more than one of these dashboards, you may find it useful to create a Pi-hole Dashboards Folder in groundcover.

View all custom metrics

Back to integrations overview

Link
Link
Link
Link
Link
quick guide