diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-11-28 04:53:08 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2019-11-28 04:53:08 +0000 |
| commit | 315e0143f65da3485dcbcd2f6a3172a351618aec (patch) | |
| tree | b713ae472cffab249c95917c6fb6d242d54e0a87 /docs | |
| parent | Adding upstream version 1.18.1. (diff) | |
| download | netdata-315e0143f65da3485dcbcd2f6a3172a351618aec.tar.xz netdata-315e0143f65da3485dcbcd2f6a3172a351618aec.zip | |
Adding upstream version 1.19.0.upstream/1.19.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Running-behind-nginx.md | 4 | ||||
| -rw-r--r-- | docs/contributing/contributing-documentation.md | 2 | ||||
| -rw-r--r-- | docs/contributing/style-guide.md | 2 | ||||
| -rw-r--r-- | docs/getting-started.md | 9 | ||||
| -rw-r--r-- | docs/netdata-cloud/README.md | 2 | ||||
| -rw-r--r-- | docs/netdata-cloud/nodes-view.md | 2 | ||||
| -rw-r--r-- | docs/netdata-cloud/signing-in.md | 2 | ||||
| -rw-r--r-- | docs/netdata-security.md | 2 | ||||
| -rw-r--r-- | docs/tutorials/dimension-templates.md | 2 | ||||
| -rw-r--r-- | docs/tutorials/longer-metrics-storage.md | 2 | ||||
| -rw-r--r-- | docs/tutorials/monitor-hadoop-cluster.md | 2 |
11 files changed, 24 insertions, 7 deletions
diff --git a/docs/Running-behind-nginx.md b/docs/Running-behind-nginx.md index cad41626..99e5e601 100644 --- a/docs/Running-behind-nginx.md +++ b/docs/Running-behind-nginx.md @@ -205,7 +205,7 @@ You can also use a unix domain socket. This will also provide a faster route bet ``` [web] - bind to = unix:/tmp/netdata.sock + bind to = unix:/var/run/netdata/netdata.sock ``` *note: Netdata v1.8+ support unix domain sockets* @@ -214,7 +214,7 @@ At the Nginx side, use something like this to use the same unix domain socket: ```conf upstream backend { - server unix:/tmp/netdata.sock; + server unix:/var/run/netdata/netdata.sock; keepalive 64; } ``` diff --git a/docs/contributing/contributing-documentation.md b/docs/contributing/contributing-documentation.md index 6f94d5bf..ebdffdbf 100644 --- a/docs/contributing/contributing-documentation.md +++ b/docs/contributing/contributing-documentation.md @@ -188,3 +188,5 @@ We may point to specific sections and ask for additional information or other fi ## What's next - Read up on the Netdata documentation [style guide](style-guide.md). + +[](<>) diff --git a/docs/contributing/style-guide.md b/docs/contributing/style-guide.md index 42c98101..5ccd250e 100644 --- a/docs/contributing/style-guide.md +++ b/docs/contributing/style-guide.md @@ -315,3 +315,5 @@ In Markdown, use the standard image syntax, `![]()`, and place the alt text betw #### Images of text Don't use images of text, code samples, or terminal output. Instead, put that text content in a code block so that all devices can render it clearly and screen readers can parse it. + +[](<>) diff --git a/docs/getting-started.md b/docs/getting-started.md index 44e25738..065da1c7 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -159,10 +159,11 @@ Find the `SEND_EMAIL="YES"` line and change it to `SEND_EMAIL="NO"`. ## Change how long Netdata stores metrics -By default, Netdata uses a database engine uses RAM to store recent metrics. For long-term metrics storage, the database -engine uses a "spill to disk" feature that also takes advantage of available disk space and keeps RAM usage low. +By default, Netdata uses a custom database which uses both RAM and the disk to store metrics. Recent metrics are stored +in the system's RAM to keep access fast, while historical metrics are "spilled" to disk to keep RAM usage low. -The database engine allows you to store a much larger dataset than your system's available RAM. +This custom database, which we call the _database engine_, allows you to store a much larger dataset than your system's +available RAM. If you're not sure whether you're using the database engine, or want to tweak the default settings to store even more historical metrics, check out our tutorial: [**Changing how long Netdata stores @@ -229,4 +230,4 @@ Take a look at some more advanced features and configurations: Or, learn more about how you can contribute to [Netdata core](../CONTRIBUTING.md) or our [documentation](../docs/contributing/contributing-documentation.md)! -[](<>) +[](<>) diff --git a/docs/netdata-cloud/README.md b/docs/netdata-cloud/README.md index 92084c3c..9ed6330b 100644 --- a/docs/netdata-cloud/README.md +++ b/docs/netdata-cloud/README.md @@ -42,3 +42,5 @@ Netdata Cloud is entirely optional. The application will never force you to crea ## Running Netdata Cloud on-premises or as a hosted instance We plan on making both on-premises and hosted instances of Netdata Cloud available to enterprises. Until then, we are creating a list of people and businesses interested in either of these options. To add yourself or your organization to this list, email us at [info@netdata.cloud](mailto:info@netdata.cloud). + +[](<>) diff --git a/docs/netdata-cloud/nodes-view.md b/docs/netdata-cloud/nodes-view.md index ec09821c..1e91639d 100644 --- a/docs/netdata-cloud/nodes-view.md +++ b/docs/netdata-cloud/nodes-view.md @@ -204,3 +204,5 @@ These services will appear under the _Messaging_ selector beneath the _Services_ | --- | --- | --- | --- | --- | | RabbitMQ | `python.d.plugin:rabbitmq`, `go.d.plugin:rabbitmq` | `rabbitmq.queued_messages` | `rabbitmq.erlang_run_queue` | | Beanstalkd | `python.d.plugin:beanstalk` | `beanstalk.total_jobs_rate` | `beanstalk.connections_rate` | `beanstalk.current_tubes` | + +[](<>) diff --git a/docs/netdata-cloud/signing-in.md b/docs/netdata-cloud/signing-in.md index 6e9e334a..03bcd01c 100644 --- a/docs/netdata-cloud/signing-in.md +++ b/docs/netdata-cloud/signing-in.md @@ -153,3 +153,5 @@ Now, when you visit the Nodes View, you will be able to see all the nodes that w ## What's next? Learn how to use the [Nodes View](nodes-view.md) to monitor many nodes concurrently. + +[](<>) diff --git a/docs/netdata-security.md b/docs/netdata-security.md index 59c1ae29..50d91df0 100644 --- a/docs/netdata-security.md +++ b/docs/netdata-security.md @@ -123,7 +123,7 @@ to IP addresses within the `160.1.x.x` range and that reverse DNS is setup for t #### Use an authenticating web server in proxy mode -Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind [nginx](Running-behind-nginx.md), [Apache](Running-behind-apache.md), [lighthttpd](Running-behind-lighttpd.md#netdata-via-lighttpd-v14x) and [Caddy](Running-behind-caddy.md#netdata-via-caddy). +Use one web server to provide authentication in front of **all your Netdata servers**. So, you will be accessing all your Netdata with URLs like `http://{HOST}/netdata/{NETDATA_HOSTNAME}/` and authentication will be shared among all of them (you will sign-in once for all your servers). Instructions are provided on how to set the proxy configuration to have Netdata run behind [nginx](Running-behind-nginx.md), [Apache](Running-behind-apache.md), [lighthttpd](Running-behind-lighttpd.md) and [Caddy](Running-behind-caddy.md). To use this method, you should firewall protect all your Netdata servers, so that only the web server IP will allowed to directly access Netdata. To do this, run this on each of your servers (or use your firewall manager): diff --git a/docs/tutorials/dimension-templates.md b/docs/tutorials/dimension-templates.md index 67648b9d..741a8d70 100644 --- a/docs/tutorials/dimension-templates.md +++ b/docs/tutorials/dimension-templates.md @@ -167,3 +167,5 @@ Or, at the very least, simplify your configuration files. For information about other advanced features in Netdata's health monitoring toolkit, check out our [health documentation](../../health/). And if you have some cool alarms you built using dimension templates, + +[](<>) diff --git a/docs/tutorials/longer-metrics-storage.md b/docs/tutorials/longer-metrics-storage.md index 1ef3f8d8..fb64ca01 100644 --- a/docs/tutorials/longer-metrics-storage.md +++ b/docs/tutorials/longer-metrics-storage.md @@ -154,3 +154,5 @@ charts](../../web/README.md#using-charts). And if you'd now like to reduce Netdata's resource usage, view our [performance guide](../../docs/Performance.md) for our best practices on optimization. + +[](<>) diff --git a/docs/tutorials/monitor-hadoop-cluster.md b/docs/tutorials/monitor-hadoop-cluster.md index 6d6e7970..f5f3315a 100644 --- a/docs/tutorials/monitor-hadoop-cluster.md +++ b/docs/tutorials/monitor-hadoop-cluster.md @@ -195,3 +195,5 @@ issue](https://github.com/netdata/netdata/issues/new?labels=bug%2C+needs+triage& - Read up on the [Zookeeper configuration file](https://github.com/netdata/go.d.plugin/blob/master/config/go.d/zookeeper.conf) to understand how to configure global options or per-job options, timeouts, TLS certificates, and more. + +[](<>) |