summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorIlya Mashchenko <ilya@netdata.cloud>2022-05-11 13:06:06 +0300
committerGitHub <noreply@github.com>2022-05-11 13:06:06 +0300
commitdd313048f6907e052cc8da2a5d001ad35635ee25 (patch)
tree72e1b513c44f1b30cc730c1883af9659dd03b292 /docs
parent156a4b05000af01f6b225af7af6f76aebfb42f35 (diff)
docs: fix unresolved file references (#12872)
Diffstat (limited to 'docs')
-rw-r--r--docs/dashboard/customize.mdx2
-rw-r--r--docs/dashboard/import-export-print-snapshot.mdx2
-rw-r--r--docs/dashboard/reference-web-server.mdx10
3 files changed, 7 insertions, 7 deletions
diff --git a/docs/dashboard/customize.mdx b/docs/dashboard/customize.mdx
index c06f62e84d..8f0b222f22 100644
--- a/docs/dashboard/customize.mdx
+++ b/docs/dashboard/customize.mdx
@@ -32,7 +32,7 @@ Click this toggle to move the legend to the _right_ of charts.
Find this setting under the **Visual** tab. Choose between Dark (the default) and White.
-## Customize the standard dashboard
+## Customize the standard dashboard info
Netdata stores information about individual charts in the `dashboard_info.js` file. This file includes section and
subsection headings, descriptions, colors, titles, tooltips, and other information for Netdata to render on the
diff --git a/docs/dashboard/import-export-print-snapshot.mdx b/docs/dashboard/import-export-print-snapshot.mdx
index dfcf80e21d..df43feb0ff 100644
--- a/docs/dashboard/import-export-print-snapshot.mdx
+++ b/docs/dashboard/import-export-print-snapshot.mdx
@@ -12,7 +12,7 @@ node running Netdata. Or, you can create a print-ready version of your dashboard
paper.
Snapshots can be incredibly useful for diagnosing anomalies after they've already happened. Let's say Netdata triggered a warning alarm while you were asleep. In the morning, you can [select the
-timeframe](/docs/dashboard/select-timeframes.mdx) when the alarm triggered, export a snapshot, and send it to a
+timeframe](/docs/dashboard/visualization-date-and-time-controls.mdx) when the alarm triggered, export a snapshot, and send it to a
colleague for further analysis.
diff --git a/docs/dashboard/reference-web-server.mdx b/docs/dashboard/reference-web-server.mdx
index ea211fd9c8..55e761a235 100644
--- a/docs/dashboard/reference-web-server.mdx
+++ b/docs/dashboard/reference-web-server.mdx
@@ -28,9 +28,9 @@ Scroll down to the `[web]` section to find the following settings.
## Settings
| Setting | Default | Description |
-| :----------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `ssl key` | `/etc/netdata/ssl/key.pem` | Declare the location of an SSL key to [enable HTTPS](#enable-HTTPSTLS-support). |
-| `ssl certificate` | `/etc/netdata/ssl/cert.pem` | Declare the location of an SSL certificate to [enable HTTPS](#enable-HTTPSTLS-support). |
+|:-------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `ssl key` | `/etc/netdata/ssl/key.pem` | Declare the location of an SSL key to [enable HTTPS](#enable-httpstls-support). |
+| `ssl certificate` | `/etc/netdata/ssl/cert.pem` | Declare the location of an SSL certificate to [enable HTTPS](#enable-httpstls-support). |
| `tls version` | `1.3` | Choose which TLS version to use. While all versions are allowed (`1` or `1.0`, `1.1`, `1.2` and `1.3`), we recommend `1.3` for the most secure encryption. If left blank, Netdata uses the highest available protocol version on your system. |
| `tls ciphers` | `none` | Choose which TLS cipher to use. Options include `TLS_AES_256_GCM_SHA384`, `TLS_CHACHA20_POLY1305_SHA256`, and `TLS_AES_128_GCM_SHA256`. If left blank, Netdata uses the default cipher list for that protocol provided by your TLS implementation. |
| `ses max window` | `15` | See [single exponential smoothing](/web/api/queries/ses/README.md). |
@@ -45,7 +45,7 @@ Scroll down to the `[web]` section to find the following settings.
| `accept a streaming request every seconds` | `0` | Can be used to set a limit on how often a parent node will accept streaming requests from child nodes in a [streaming and replication setup](/streaming/README.md). |
| `respect do not track policy` | `no` | If set to `yes`, Netdata will respect the user's browser preferences for [Do Not Track](https://www.eff.org/issues/do-not-track) (DNT) and storing cookies. If DNT is _enabled_ in the browser, and this option is set to `yes`, users will not be able to sign in to Netdata Cloud via their local Agent dashboard, and their node will not connect to any [registry](/registry/README.md). For certain browsers, users must disable DNT and change this option to `yes` for full functionality. |
| `x-frame-options response header` | ` ` | Avoid [clickjacking attacks](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options), by ensuring that the content is not embedded into other sites. |
-| `allow connections from` | `localhost *` | Declare which IP addresses or full-qualified domain names (FQDNs) are allowed to connect to the web server, including the [dashboard](/docs/dashboard/dashboards-charts.mdx) or [HTTP API](/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
+| `allow connections from` | `localhost *` | Declare which IP addresses or full-qualified domain names (FQDNs) are allowed to connect to the web server, including the [dashboard](/docs/dashboard/interact-charts.mdx) or [HTTP API](/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
| `allow connections by dns` | `heuristic` | See the [access list examples](#access-lists) for details on using `allow` settings. |
| `allow dashboard from` | `localhost *` | |
| `allow dashboard by dns` | `heuristic` | |
@@ -62,7 +62,7 @@ Scroll down to the `[web]` section to find the following settings.
| `gzip compression level` | `3` | Valid settings are 1 (fastest) to 9 (best ratio). |
| `web server threads` | ` ` | How many processor threads the web server is allowed. The default is system-specific, the minimum of `6` or the number of CPU cores. |
| `web server max sockets` | ` ` | Available sockets. The default is system-specific, automatically adjusted to 50% of the max number of open files Netdata is allowed to use (via `/etc/security/limits.conf` or systemd), to allow enough file descriptors to be available for data collection. |
-| `custom dashboard_info.js` | ` ` | Specifies the location of a custom `dashboard.js` file. See [customizing the standard dashboard](/docs/dashboard/customize.mdx#customize-the-standard-dashboard) for details. |
+| `custom dashboard_info.js` | ` ` | Specifies the location of a custom `dashboard.js` file. See [customizing the standard dashboard](/docs/dashboard/customize.mdx#customize-the-standard-dashboard) for details. |
## Examples