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

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/charts.d.plugin/ap/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/charts.d.plugin/ap/metadata.yaml" sidebar_label: "Access Points" learn_status: "Published" learnrelpath: "Collecting Metrics/Linux Systems/Network" 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/network-wired.svg" width="150"/> Plugin: charts.d.plugin Module: ap <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> The ap collector visualizes data related to wireless access points. It uses the `iw` command line utility to detect access points. For each interface that is of `type AP`, it then runs `iw INTERFACE station dump` and collects statistics. This collector is only supported on the following platforms: Linux This collector only supports collecting metrics from a single instance of this integration. The plugin is able to auto-detect if you are running access points on your linux box. 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 | |:|:-|:-| | ap.clients | clients | clients | | ap.net | received, sent | kilobits/s | | ap.packets | received, sent | packets/s | | ap.issues | retries, failures | issues/s | | ap.signal | average signal | dBm | | ap.bitrate | receive, transmit, expected | Mbps | There are no alerts configured by default for this integration. If , make sure `netdata-plugin-chartsd` is installed. Make sure the `iw` utility is installed. The configuration file name for this integration is `charts.d/ap.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 charts.d/ap.conf ``` The config file is sourced by the charts.d plugin. It's a standard bash file. The following collapsed table contains all the options that can be configured for the ap collector. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | apupdateevery | The data collection frequency. If unset, will inherit the netdata update frequency. | 1 | no | | ap_priority | Controls the order of charts at the netdata dashboard. | 6900 | no | | ap_retries | The number of retries to do in case of failure before disabling the collector. | 10 | no | </details> Specify a custom collection frequence (update_every) for this collector ```yaml apupdateevery=10 ``` To troubleshoot issues with the `ap` collector, run the `charts.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 `charts.d.plugin` to debug the collector: ```bash ./charts.d.plugin debug 1 ap ```