Project: Netdata (Observability and Analysis / Observability)
File: isc_dhcp.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/isc_dhcpd/README.md" metayaml: "https://github.com/netdata/netdata/edit/master/src/go/collectors/go.d.plugin/modules/iscdhcpd/metadata.yaml" sidebar_label: "ISC DHCP" learn_status: "Published" learnrelpath: "Collecting Metrics/DNS and DHCP Servers" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> <img src="https://netdata.cloud/img/isc.png" width="150"/> Plugin: go.d.plugin Module: isc_dhcpd <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This collector monitors ISC DHCP lease usage by reading the DHCP client lease database (dhcpd.leases). This collector is supported on all platforms. This collector supports collecting metrics from multiple instances of this integration, including remote instances. This integration doesn't support auto-detection. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. These metrics refer to the entire monitored application. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | iscdhcpd.activeleases_total | active | leases | These metrics refer to the DHCP pool. Labels: | Label | Description | |:--|:-| | dhcppoolname | The DHCP pool name defined in the collector configuration. | Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | iscdhcpd.dhcppool_utilization | utilization | percent | | iscdhcpd.dhcppoolactiveleases | active | leases | There are no alerts configured by default for this integration. No action required. The configuration file name for this integration is `go.d/isc_dhcpd.conf`. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config go.d/isc_dhcpd.conf ``` The following options can be defined globally: updateevery, autodetectionretry. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | update_every | Data collection frequency. | 1 | no | | autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no | | leases_path | Path to DHCP client lease database. | /var/lib/dhcp/dhcpd.leases | no | | pools | List of IP pools to monitor. | | yes | List of IP pools to monitor. IP range syntax: see . Syntax: ```yaml pools: name: "POOL_NAME1" networks: "SPACE SEPARATED LIST OF IP RANGES" name: "POOL_NAME2" networks: "SPACE SEPARATED LIST OF IP RANGES" ``` </details> A basic example configuration. <details><summary>Config</summary> ```yaml jobs: name: local pools: name: lan networks: "192.168.0.0/24 192.168.1.0/24 192.168.2.0/24" name: wifi networks: "10.0.0.0/24" ``` </details> To troubleshoot issues with the `isc_dhcpd` collector, run the `go.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. ```bash cd /usr/libexec/netdata/plugins.d/ ``` Switch to the `netdata` user. ```bash sudo -u netdata -s ``` Run the `go.d.plugin` to debug the collector: ```bash ./go.d.plugin -d -m isc_dhcpd ```