Make title reflect legacy agent dashboard (#15479)
Fotis Voutsas committed
Jul 25, 2023 at 13:31 UTC
f0ba9fa201f9ab339b5d4f2f981ad2ecf93d7939
5 files changed
+4
-19
docs/anonymous-statistics.md
+1
-1
@@ -23,7 +23,7 @@ We use the statistics gathered from this information for two purposes:
23
24
Netdata collects usage information via two different channels:
25
26
-- **Agent dashboard**: We use the [PostHog JavaScript integration](https://posthog.com/docs/integrations/js-integration) (with sensitive event attributes overwritten to be anonymized) to send product usage events when you access an [Agent's dashboard](https://github.com/netdata/netdata/blob/master/web/gui/README.md).
26
+- **Agent dashboard**: We use the [PostHog JavaScript integration](https://posthog.com/docs/integrations/js-integration) (with sensitive event attributes overwritten to be anonymized) to send product usage events when you access an [Agent's dashboard](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/accessing-netdata-dashboards.md).
27
- **Agent backend**: The `netdata` daemon executes the [`anonymous-statistics.sh`](https://github.com/netdata/netdata/blob/6469cf92724644f5facf343e4bdd76ac0551a418/daemon/anonymous-statistics.sh.in) script when Netdata starts, stops cleanly, or fails.
28
29
You can opt-out from sending anonymous statistics to Netdata through three different [opt-out mechanisms](#opt-out).
docs/configure/common-changes.md
+1
-1
@@ -20,7 +20,7 @@ directory.
20
21
## Change dashboards and visualizations
22
23
-The Netdata Agent's [local dashboard](https://github.com/netdata/netdata/blob/master/web/gui/README.md), accessible
23
+The Netdata Agent's [local dashboard](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/accessing-netdata-dashboards.md), accessible
24
at `http://NODE:19999` is highly configurable. If
25
you use Netdata Cloud
26
for [infrastructure monitoring](https://github.com/netdata/netdata/blob/master/docs/quickstart/infrastructure.md), you
packaging/installer/README.md
-6
@@ -38,12 +38,6 @@ but we have some hints on what you might want to do next.
38
Explore our [general advanced installation options and troubleshooting](#advanced-installation-options-and-troubleshooting), specific options
39
for the [single line installer](#install-on-linux-with-one-line-installer), or [other installation methods](#other-installation-methods).
40
41
-#### Agent user interface
42
-
43
-To access the UI provided by the locally installed agent, open a browser and navigate to `http://NODE:19999`, replacing `NODE` with either `localhost` or
44
-the hostname/IP address of the remote node. You can also read more about
45
-[the agent dashboard](https://github.com/netdata/netdata/blob/master/web/gui/README.md).
46
-
41
#### Configuration
42
43
Discover the recommended way to [configure Netdata's settings or behavior](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md) using our built-in
web/gui/README.md
+1
-10
@@ -1,13 +1,4 @@
1
-<!--
2
-title: "Local Agent dashboard"
3
-description: "The local Netdata Agent dashboard is the heart of health monitoring and performance troubleshooting, with hundreds of real-time charts."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/web/gui/README.md
5
-sidebar_label: "Local Agent dashboard"
6
-learn_status: "Published"
7
-learn_rel_path: "Operations"
8
--->
9
-
10
-# Local Agent dashboard
1
+# Legacy Agent dashboard
2
3
> ⚠️ You're checking the documentation for the legacy Agent dashboard. For the current version please check [Accessing Netdata Dashboards](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/accessing-netdata-dashboards.md).
4
web/server/README.md
+1
-1
@@ -48,7 +48,7 @@ Scroll down to the `[web]` section to find the following settings.
48
| `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](https://github.com/netdata/netdata/blob/master/streaming/README.md). |
49
| `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](https://github.com/netdata/netdata/blob/master/registry/README.md). For certain browsers, users must disable DNT and change this option to `yes` for full functionality. |
50
| `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. |
51
-| `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](https://github.com/netdata/netdata/blob/master/web/gui/README.md) or [HTTP API](https://github.com/netdata/netdata/blob/master/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
51
+| `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](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/accessing-netdata-dashboards.md) or [HTTP API](https://github.com/netdata/netdata/blob/master/web/api/README.md). This is a global setting with higher priority to any of the ones below. |
52
| `allow connections by dns` | `heuristic` | See the [access list examples](#access-lists) for details on using `allow` settings. |
53
| `allow dashboard from` | `localhost *` | |
54
| `allow dashboard by dns` | `heuristic` | |