This exporter exports some variables from an AVM Fritzbox to prometheus.
This exporter is tested with a Fritzbox 7590 software version 07.12, 07.20, 07.21 and 07.25.
The goal of the fork is:
- allow passing of username / password using evironment variable
- use https instead of http for communitcation with fritz.box
- move config of metrics to be exported to config file rather then code
- add config for additional metrics to collect (especially from TR-064 API)
- create a grafana dashboard consuming the additional metrics
- collect metrics from lua APIs not available in UPNP APIs
Other changes:
- replaced digest authentication code with own implementation
- improved error messages
- test mode prints details about all SOAP Actions and their parameters
- collect option to directly test collection of results
- additional metrics to collect details about connected hosts and DECT devices
- support to use results like hostname or MAC address as labels to metrics
- support for metrics from lua APIs (e.g. CPU temperature, utilization, ...)
go get github.com/sberk42/fritzbox_exporter/
cd $GOPATH/src/github.com/sberk42/fritzbox_exporter
go install
In the configuration of the Fritzbox the option "Statusinformationen über UPnP übertragen" in the dialog "Heimnetz > Heimnetzübersicht > Netzwerkeinstellungen" has to be enabled.
First you have to build the container: docker build --tag fritzbox-prometheus-exporter:latest .
Then start the container:
$ docker run -e 'USERNAME=your_fritzbox_username' \
-e 'PASSWORD=your_fritzbox_password' \
-e 'GATEWAY_URL="http://192.168.0.1:49000"' \
-e 'LISTEN_ADDRESS="0.0.0.0:9042"' \
fritzbox-prometheus-exporter:latest
I've you're getting no such host
issues, define your FritzBox as DNS server for your docker container like this:
$ docker run --dns YOUR_FRITZBOX_IP \
-e 'USERNAME=your_fritzbox_username' \
-e 'PASSWORD=your_fritzbox_password' \
-e 'GATEWAY_URL="http://192.168.0.1:49000"' \
-e 'LISTEN_ADDRESS="0.0.0.0:9042"' \
fritzbox-prometheus-exporter:latest
Set your environment variables within the docker-compose.yml file.
Then start up the container using docker-compose up -d
.
Usage:
$GOPATH/bin/fritzbox_exporter -h
Usage of ./fritzbox_exporter:
-gateway-url string
The URL of the FRITZ!Box (default "http://fritz.box:49000")
-gateway-luaurl string
The URL of the FRITZ!Box UI (default "http://fritz.box")
-metrics-file string
The JSON file with the metric definitions. (default "metrics.json")
-lua-metrics-file string
The JSON file with the lua metric definitions. (default "metrics-lua.json")
-test
print all available SOAP calls and their results (if call possible) to stdout
-json-out string
store metrics also to JSON file when running test
-testLua
read luaTest.json file make all contained calls and dump results
-collect
collect metrics once print to stdout and exit
-nolua
disable collecting lua metrics
-username string
The user for the FRITZ!Box UPnP service
-password string
The password for the FRITZ!Box UPnP service
-listen-address string
The address to listen on for HTTP requests. (default "127.0.0.1:9042")
The password (needed for metrics from TR-064 API) can be passed over environment variables to test in shell:
read -rs PASSWORD && export PASSWORD && ./fritzbox_exporter -username <user> -test; unset PASSWORD
start exporter and run curl -s http://127.0.0.1:9042/metrics
The exporter prints all available Variables to stdout when called with the -test option. These values are determined by parsing all services from http://fritz.box:49000/igddesc.xml and http://fritzbox:49000/tr64desc.xml (for TR64 username and password is needed!!!)
The metrics to collect are no longer hard coded, but have been moved to the metrics.json and metrics-lua.json files, so just adjust to your needs. For a list of all the available metrics just execute the exporter with -test (username and password are needed for the TR-064 API!) For lua metrics open UI in browser and check the json files used for the various screens.
For a list of all available metrics, see the dumps below (the format is the same as in the metrics.json file, so it can be used to easily add further metrics to retrieve):
The dashboard is now also published on Grafana.