diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Add-more-charts-to-netdata.md | 2 | ||||
| -rw-r--r-- | docs/Charts.md | 2 | ||||
| -rw-r--r-- | docs/Demo-Sites.md | 2 | ||||
| -rw-r--r-- | docs/Donations-netdata-has-received.md | 2 | ||||
| -rw-r--r-- | docs/GettingStarted.md | 2 | ||||
| -rw-r--r-- | docs/Netdata-Security-and-Disclosure-Information.md | 2 | ||||
| -rw-r--r-- | docs/Performance.md | 2 | ||||
| -rw-r--r-- | docs/Running-behind-apache.md | 2 | ||||
| -rw-r--r-- | docs/Running-behind-caddy.md | 2 | ||||
| -rw-r--r-- | docs/Running-behind-lighttpd.md | 2 | ||||
| -rw-r--r-- | docs/Running-behind-nginx.md | 2 | ||||
| -rw-r--r-- | docs/Third-Party-Plugins.md | 2 | ||||
| -rw-r--r-- | docs/Why-Netdata.md | 2 | ||||
| -rw-r--r-- | docs/a-github-star-is-important.md | 2 | ||||
| -rw-r--r-- | docs/configuration-guide.md | 2 | ||||
| -rwxr-xr-x | docs/generator/buildhtml.sh | 5 | ||||
| -rw-r--r-- | docs/high-performance-netdata.md | 2 | ||||
| -rw-r--r-- | docs/netdata-for-IoT.md | 2 | ||||
| -rw-r--r-- | docs/netdata-security.md | 2 | ||||
| -rw-r--r-- | docs/privacy-policy.md | 2 | ||||
| -rw-r--r-- | docs/terms-of-use.md | 2 |
21 files changed, 44 insertions, 1 deletions
diff --git a/docs/Add-more-charts-to-netdata.md b/docs/Add-more-charts-to-netdata.md index 1512a25e78..c890b92341 100644 --- a/docs/Add-more-charts-to-netdata.md +++ b/docs/Add-more-charts-to-netdata.md @@ -427,3 +427,5 @@ application|language|notes| :---------:|:------:|:----| example|BASH<br/>Shell Script|Skeleton plugin in BASH.<br/><br/>DEPRECATED IN FAVOR OF THE PYTHON ONE. It is still supplied only as an example module to shell scripting plugins.<br/> <br/>netdata plugin: [charts.d.plugin](../collectors/charts.d.plugin#chartsdplugin)<br/>plugin module: [example.chart.sh](../collectors/charts.d.plugin/example)<br/>configuration file: [charts.d/example.conf](../collectors/charts.d.plugin/example)| example|python<br/>v2 or v3|Skeleton plugin in Python.<br/> <br/>netdata plugin: [python.d.plugin](../collectors/python.d.plugin)<br/>plugin module: [example.chart.py](../collectors/python.d.plugin/example)<br/>configuration file: [python.d/example.conf](../collectors/python.d.plugin/example)| + +[]() diff --git a/docs/Charts.md b/docs/Charts.md index d5080ce1fe..66be03be5e 100644 --- a/docs/Charts.md +++ b/docs/Charts.md @@ -23,3 +23,5 @@ The reasoning behind calling these instances "families" is that different charts A context is a grouping of identical charts, for each instance of the hardware or software monitored. For example, `health/health.d/net.conf` refers to four contexts: `net.drops`, `net.fifo`, `net.net`, `net.packets`. You can see the context of a chart if you hover over the date right above the dimensions of the chart. The line that appears shows you two things: the collector that produces the chart and the chart context. For example, let's take the `net.packets` context. You will see on the dashboard as many charts with context net.packets as you have network interfaces (families). These charts will be named `net_packets.[family]`. For the example of the two interfaces `eth0` and `eth1`, you will see charts named `net_packets.eth0` and `net_packets.eth1`. Both of these charts show the exact same dimensions, but for different instances of a network interface. + +[]() diff --git a/docs/Demo-Sites.md b/docs/Demo-Sites.md index e20db47fe8..f6aad1398b 100644 --- a/docs/Demo-Sites.md +++ b/docs/Demo-Sites.md @@ -17,3 +17,5 @@ Singapore|**[singapore.my-netdata.io](https://singapore.my-netdata.io)**|[**|[](https://toronto.my-netdata.io)|[DigitalOcean.com](https://m.do.co/c/83dc9f941745) *Netdata dashboards are mobile and touch friendly.* + +[]() diff --git a/docs/Donations-netdata-has-received.md b/docs/Donations-netdata-has-received.md index 9092fb7f4e..3c737be8a1 100644 --- a/docs/Donations-netdata-has-received.md +++ b/docs/Donations-netdata-has-received.md @@ -21,3 +21,5 @@ Thank you! **Do you want to donate?** We are thirsty for on-line services that can help us make netdata better. We also try to build a network of demo sites (VMs) that can help us show the full potential of netdata. Please contact me at costa@tsaousis.gr. + +[]() diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md index c16700d9de..b3d037bb07 100644 --- a/docs/GettingStarted.md +++ b/docs/GettingStarted.md @@ -178,3 +178,5 @@ and set `SEND_EMAIL="NO"`. - Check [Health Monitoring](../health) for configuring your own alarms, or setting up alarm notifications. - Check [Streaming](../streaming) for centralizing netdata metrics. - Check [Backends](../backends) for long term archiving of netdata metrics to time-series databases. + +[]() diff --git a/docs/Netdata-Security-and-Disclosure-Information.md b/docs/Netdata-Security-and-Disclosure-Information.md index 86adfeeb93..8e8a66afc7 100644 --- a/docs/Netdata-Security-and-Disclosure-Information.md +++ b/docs/Netdata-Security-and-Disclosure-Information.md @@ -35,3 +35,5 @@ As the security issue moves from triage, to identified fix, to release planning ## Public Disclosure Timing A public disclosure date is negotiated by the Netdata team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Netdata team holds the final say when setting a disclosure date. + +[]() diff --git a/docs/Performance.md b/docs/Performance.md index 7ed7330225..629fcbf699 100644 --- a/docs/Performance.md +++ b/docs/Performance.md @@ -231,3 +231,5 @@ Finally, if no web server is installed on your device, you can use port tcp/80 f [web] port = 80 ``` + +[]() diff --git a/docs/Running-behind-apache.md b/docs/Running-behind-apache.md index 775bcf2fe9..7838665cde 100644 --- a/docs/Running-behind-apache.md +++ b/docs/Running-behind-apache.md @@ -266,3 +266,5 @@ Make sure the requests reach netdata, by examing `/var/log/netdata/access.log`. 1. if the requests do not reach netdata, your apache does not forward them. 2. if the requests reach netdata by the URLs are wrong, you have not re-written them properly. + +[]() diff --git a/docs/Running-behind-caddy.md b/docs/Running-behind-caddy.md index 135610282b..1b25b0a2e1 100644 --- a/docs/Running-behind-caddy.md +++ b/docs/Running-behind-caddy.md @@ -25,3 +25,5 @@ netdata.domain.tld { You would also need to instruct netdata to listen only to `127.0.0.1` or `::1`. To limit access to netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`. + +[]() diff --git a/docs/Running-behind-lighttpd.md b/docs/Running-behind-lighttpd.md index a195c8fa80..5c74439ad1 100644 --- a/docs/Running-behind-lighttpd.md +++ b/docs/Running-behind-lighttpd.md @@ -58,3 +58,5 @@ enable web responses gzip compression = no You would also need to instruct netdata to listen only to `127.0.0.1` or `::1`. To limit access to netdata only from localhost, set `bind socket to IP = 127.0.0.1` or `bind socket to IP = ::1` in `/etc/netdata/netdata.conf`. + +[]() diff --git a/docs/Running-behind-nginx.md b/docs/Running-behind-nginx.md index 505bad81d6..3918af2436 100644 --- a/docs/Running-behind-nginx.md +++ b/docs/Running-behind-nginx.md @@ -200,3 +200,5 @@ If you get an 502 Bad Gateway error you might check your nginx error log: ``` If you see something like the above, chances are high that SELinux prevents nginx from connecting to the backend server. To fix that, just use this policy: `setsebool -P httpd_can_network_connect true`. + +[]() diff --git a/docs/Third-Party-Plugins.md b/docs/Third-Party-Plugins.md index 3e58bfb9ac..38fa90e4ed 100644 --- a/docs/Third-Party-Plugins.md +++ b/docs/Third-Party-Plugins.md @@ -27,3 +27,5 @@ Collect [number of currently logged-on users](https://github.com/veksh/netdata-n ## Nim There is an unofficial [nim plugin helper](https://github.com/FedericoCeratto/nim-netdata-plugin) + +[]() diff --git a/docs/Why-Netdata.md b/docs/Why-Netdata.md index 57ff722ec6..5d290e01a4 100644 --- a/docs/Why-Netdata.md +++ b/docs/Why-Netdata.md @@ -168,3 +168,5 @@ Of course, there are a few issues that need to be addressed with this approach: Our approach uses the netdata [registry](../registry/). The registry solves the problem of maintaining a list of all the netdata installations we have. It does this transparently, without any configuration. It tracks the netdata servers your web browser has visited and bookmarks them at the `my-netdata` menu. Every netdata can be a registry. You can use the global one we provided for free, or pick one of your netdata servers and turn it to a registry for your network. + +[]() diff --git a/docs/a-github-star-is-important.md b/docs/a-github-star-is-important.md index ab20331954..e46d564492 100644 --- a/docs/a-github-star-is-important.md +++ b/docs/a-github-star-is-important.md @@ -11,3 +11,5 @@ So, give netdata a **GitHub star**, at the top right of this page. Thank you! Costa Tsaousis + +[]() diff --git a/docs/configuration-guide.md b/docs/configuration-guide.md index 78691c7d75..511632b6ef 100644 --- a/docs/configuration-guide.md +++ b/docs/configuration-guide.md @@ -114,3 +114,5 @@ Last, what about options you believe you have set, but you misspelled?When you g Unix prefers regular expressions. But they are just too hard, too cryptic to use, write and understand. So, netdata supports [simple patterns](../libnetdata/simple_pattern/). + +[]() diff --git a/docs/generator/buildhtml.sh b/docs/generator/buildhtml.sh index 410b0fc84d..3cc87d29f8 100755 --- a/docs/generator/buildhtml.sh +++ b/docs/generator/buildhtml.sh @@ -24,7 +24,10 @@ cp -a ./${GENERATOR_DIR}/custom ./${GENERATOR_DIR}/src/ # Modify the first line of the main README.md, to enable proper static html generation echo "Modifying README header" -sed -i -e '0,/# netdata /s//# Introduction\n\n/' -e 's/\[!\[analytics.*UA-64295674-3)\]()//g' ${GENERATOR_DIR}/src/README.md +sed -i -e '0,/# netdata /s//# Introduction\n\n/' ${GENERATOR_DIR}/src/README.md + +# Remove all GA tracking code +find ${GENERATOR_DIR}/src -name "*.md" -print0 | xargs -0 sed -i -e 's/\[!\[analytics.*UA-64295674-3)\]()//g' # Remove specific files that don't belong in the documentation declare -a EXCLUDE_LIST=( diff --git a/docs/high-performance-netdata.md b/docs/high-performance-netdata.md index 1671acab8f..a9947d9bc3 100644 --- a/docs/high-performance-netdata.md +++ b/docs/high-performance-netdata.md @@ -147,3 +147,5 @@ Max open files 30000 30000 files Max open files 30000 30000 files ``` + +[]() diff --git a/docs/netdata-for-IoT.md b/docs/netdata-for-IoT.md index 515276f426..ada92d338d 100644 --- a/docs/netdata-for-IoT.md +++ b/docs/netdata-for-IoT.md @@ -37,3 +37,5 @@ sensors=force Then restart netdata. You will get this:  + +[]() diff --git a/docs/netdata-security.md b/docs/netdata-security.md index 6bfda10a88..9cbbcf426d 100644 --- a/docs/netdata-security.md +++ b/docs/netdata-security.md @@ -167,3 +167,5 @@ path|owner|permissions| netdata |comments| `/var/cache/netdata`|user `netdata`<br/>group `netdata`|dirs `0750`<br/>files `0660`|reads, writes, creates, deletes|**Netdata ephemeral database files**<br/>Netdata stores its ephemeral real-time database here. `/var/lib/netdata`|user `netdata`<br/>group `netdata`|dirs `0750`<br/>files `0660`|reads, writes, creates, deletes|**Netdata permanent database files**<br/>Netdata stores here the registry data, health alarm log db, etc. `/var/log/netdata`|user `netdata`<br/>group `root`|dirs `0755`<br/>files `0644`|writes, creates|**Netdata log files**<br/>all the Netdata applications, logs their errors or other informational messages to files in this directory. These files should be log rotated. + +[]() diff --git a/docs/privacy-policy.md b/docs/privacy-policy.md index d3c007dea6..d8f1973fc8 100644 --- a/docs/privacy-policy.md +++ b/docs/privacy-policy.md @@ -91,3 +91,5 @@ Data transferred from the European Union to the United States or outside the Eur We may occasionally update this Privacy Policy. When we do, we will provide you with notice of such update through (at a minimum) a reasonably prominent notice on the Websites and Services, and will revise the Effective Date below. We encourage you to periodically review this Privacy Policy to stay informed about how we are protecting, using, processing and transferring the personal information we collect. ***Effective Date: 10 November 2018.*** + +[]() diff --git a/docs/terms-of-use.md b/docs/terms-of-use.md index 69ed8ad0e1..378ba3e85d 100644 --- a/docs/terms-of-use.md +++ b/docs/terms-of-use.md @@ -158,3 +158,5 @@ No agency relationship: The parties agree that no joint venture, partnership, em Integration: These Master Terms and any applicable Additional Terms constitute the entire agreement between you and Netdata relating to this subject matter and supersede any and all prior communications and/or agreements between you and Netdata relating to access and use of the Services. Human-readable summary of Sec 15: If there is a lawsuit arising from these terms, it should be in Delaware and governed by Delaware law. We are glad you use our sites, but this agreement does not mean we are partners. + +[]() |