summaryrefslogtreecommitdiffstats
path: root/AUTHORS.md
AgeCommit message (Expand)Author
2021-02-05Psalm: Fix class loadingSean Molenaar
2021-02-02Controllers: Export Starred or unread instead of andSean Molenaar
2021-01-20Fetcher: Update client and add testSean Molenaar
2021-01-1715.2.0-beta2 - 2021-01-1715.2.0-beta2Benjamin Brahmer
2021-01-12Fix nc 21 phpunit issueSean Molenaar
2020-12-23Release 15.1.1-rc215.1.1-rc2Benjamin Brahmer
2020-12-17Fix mapper->find and empty user sessionsSean Molenaar
2020-11-11Release 15.1.0-rc315.1.0-rc3Benjamin Brahmer
2020-11-10Release 15.1.0-rc215.1.0-rc2Benjamin Brahmer
2020-11-10Fix unread count and related issuesSean Molenaar
2020-11-03Add migration with foreign keysSean Molenaar
2020-10-29Command: Add unittestsSean Molenaar
2020-10-10Fix usage of at() in unittestsSean Molenaar
2020-10-08Release 15.0.315.0.3Benjamin Brahmer
2020-10-05Define microtime as stringSean Molenaar
2020-10-04Release 15.0.215.0.2Benjamin Brahmer
2020-10-03Release 15.0.115.0.1Benjamin Brahmer
2020-10-03fix matching any stringBenjamin Brahmer
2020-09-27Create V2 mapper, Service and management commandsSean Molenaar
2020-09-25Require nextcloud 20 for new developmentSean Molenaar
2020-09-01js updatesBenjamin Brahmer
2020-08-30Release 14.2.014.2.0Benjamin Brahmer
2020-08-25Test on latest nextcloudSean Molenaar
2020-05-23bump versionBenjamin Brahmer
2020-05-22Release 14.1.814.1.8Benjamin Brahmer
2020-05-04update feed-io to 4.6.0 and update js packagesBenjamin Brahmer
2020-04-28Release 14.1.614.1.6Benjamin Brahmer
2020-04-28Release 14.1.5Benjamin Brahmer
2020-04-23Update for Nextcloud 19Benjamin Brahmer
2020-03-18Release 14.1.4-rc1 (#649)14.1.4-rc1Benjamin Brahmer
2020-01-11Release 14.1.1 (#614)14.1.1Benjamin Brahmer
2020-01-11update feed-io to v4.5.1Benjamin Brahmer
2019-12-27Release 14.1.0 (#597)14.1.0Benjamin Brahmer
2019-12-25Update for nextcloud 18 (#593)Benjamin Brahmer
2019-11-23Update PHP & JS packages (#575)Benjamin Brahmer
2019-10-19Release 14.0.1 (#561)14.0.1Benjamin Brahmer
2019-09-19Release 14.0.0 (#524)Benjamin Brahmer
2019-04-11Release 13.1.6 (#490)13.1.6Benjamin Brahmer
2019-03-28Release 13.1.513.1.5Benjamin Brahmer
2019-03-22Stop assuming encoding of xml, let simplexml throw silently (#457)Sean Molenaar
2019-03-18Set nextcloud user agentSean Molenaar
2019-03-17fix/allow CDATA encoding (#428)Sean Molenaar
2019-03-12Catch FeedIO reader exception.Sean Molenaar
2017-05-24update changelog and authors fileBernhard Posselt
2016-04-03move from python to php scriptsBernhard Posselt
2015-11-27improve contributing instructionsBernhard Posselt
2015-11-25update changelogBernhard Posselt
2015-11-22fix unreadable app navigationBernhard Posselt
2015-11-12update picofeedBernhard Posselt
2015-10-25update npm libsBernhard Posselt
n class="w"> go.d/unbound.conf ``` The file contains all the global and job-related parameters. The `name` setting is required, and two Unbound servers can't have the same name. > It is important you know whether your Unbound server is running in cumulative or non-cumulative mode, as a conflict > between modes will create incorrect charts. Here are two examples for local Unbound servers, which may work based on your unique setup: ```yaml jobs: - name: local address: 127.0.0.1:8953 cumulative: no use_tls: yes tls_skip_verify: yes tls_cert: /path/to/unbound_control.pem tls_key: /path/to/unbound_control.key - name: local address: 127.0.0.1:8953 cumulative: yes use_tls: no ``` Netdata will attempt to read `unbound.conf` to get the appropriate `address`, `cumulative`, `use_tls`, `tls_cert`, and `tls_key` parameters. Restart Netdata with `sudo systemctl restart netdata`, or the [appropriate method](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md#maintaining-a-netdata-agent-installation) for your system. ### Manual setup for a remote Unbound server Collecting metrics from remote Unbound servers requires manual configuration. There are too many possibilities to cover all remote connections here, but the [default `unbound.conf` file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/unbound.conf) contains a few useful examples: ```yaml jobs: - name: remote address: 203.0.113.10:8953 use_tls: no - name: remote_cumulative address: 203.0.113.11:8953 use_tls: no cumulative: yes - name: remote address: 203.0.113.10:8953 cumulative: yes use_tls: yes tls_cert: /etc/unbound/unbound_control.pem tls_key: /etc/unbound/unbound_control.key ``` To see all the available options, see the default [unbound.conf file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plugin/config/go.d/unbound.conf). ## What's next? Now that you're collecting metrics from your Unbound servers, let us know how it's working for you! There's always room for improvement or refinement based on real-world use cases. Feel free to [file an issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your thoughts.