Moved contents of get started to installer readme (#14467)
Chris Akritidis committed
Feb 8, 2023 at 06:19 UTC
9067033b16bed8855f6cd828585ed84aec204240
2 files changed
+118
-340
docs/get-started.mdx
deleted
-258
@@ -1,258 +0,0 @@
1
-<!--
2
-title: "Install Netdata"
3
-description: "Download and install the open-source Netdata monitoring agent on physical/virtual servers, Linux (Ubuntu/Debian/CentOS/etc), Docker, Kubernetes, and many others, often with one command."
4
-sidebar_label: "Install Netdata"
5
-custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/get-started.mdx"
6
-learn_status: "Published"
7
-learn_topic_type: "Tasks"
8
-learn_rel_path: "Getting started"
9
--->
10
-
11
-import { OneLineInstallWget, OneLineInstallCurl } from '@site/src/components/OneLineInstall/'
12
-import { InstallRegexLink, InstallBoxRegexLink } from '@site/src/components/InstallRegexLink/'
13
-import Tabs from '@theme/Tabs';
14
-import TabItem from '@theme/TabItem';
15
-
16
-## Get started
17
-
18
-Netdata is a free and open-source (FOSS) monitoring agent that collects thousands of hardware and software metrics from
19
-any physical or virtual system (we call them _nodes_). These metrics are organized in an easy-to-use and -navigate interface.
20
-
21
-Together with [Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx), you can monitor your entire infrastructure in
22
-real time and troubleshoot problems that threaten the health of your nodes.
23
-
24
-Netdata runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices. It
25
-runs on Linux distributions (Ubuntu, Debian, CentOS, and more), container/microservice platforms (Kubernetes clusters,
26
-Docker), and many other operating systems (FreeBSD, macOS), with no `sudo` required.
27
-
28
-To install Netdata in minutes on your platform:
29
-
30
-1. Sign up to https://app.netdata.cloud/
31
-2. You will be presented with an empty space, and a prompt to "Connect Nodes" with the install command for each platform
32
-3. Select the platform you want to install Netdata to, copy and paste the script into your node's terminal, and run it
33
-
34
-Upon installation completing successfully, you should be able to see the node live in your Netdata Space and live charts in the Overview tab. [Read more about the cloud features](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx).
35
-
36
-Where you go from here is based on your use case, immediate needs, and experience with monitoring and troubleshooting,
37
-but we have some hints on what you might want to do next.
38
-
39
-### What's next?
40
-
41
-Explore our [general advanced installation options and troubleshooting](#advanced-installation-options-and-troubleshooting), specific options for the [single line installer](#install-on-linux-with-one-line-installer), or [other installation methods](#other-installation-methods).
42
-
43
-#### Agent user interface
44
-
45
-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
46
-the hostname/IP address of the remote node. You can also read more about [how the agent dashboard works](https://github.com/netdata/netdata/blob/master/docs/dashboard/how-dashboard-works.mdx), or dive directly into the many ways
47
-to [interact with charts](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.mdx).
48
-
49
-#### Configuration
50
-
51
-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
52
-`edit-config` script, then apply that knowledge to mission-critical tweaks, such as [changing how long Netdata stores
53
-metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md).
54
-
55
-#### Data collection
56
-
57
-If Netdata didn't autodetect all the hardware, containers, services, or applications running on your node, you should
58
-learn more about [how data collectors work](https://github.com/netdata/netdata/blob/master/docs/collect/how-collectors-work.md). If there's a [supported
59
-collector](https://github.com/netdata/netdata/blob/master/collectors/COLLECTORS.md) for metrics you need, [configure the collector](https://github.com/netdata/netdata/blob/master/docs/collect/enable-configure.md)
60
-or read about its requirements to configure your endpoint to publish metrics in the correct format and endpoint.
61
-
62
-#### Alarms & notifications
63
-
64
-Netdata comes with hundreds of preconfigured alarms, designed by our monitoring gurus in parallel with our open-source
65
-community, but you may want to [edit alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/configure-alarms.md) or
66
-[enable notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) to customize your Netdata experience.
67
-
68
-#### Make your deployment production ready
69
-
70
-Both [securing Netdata](https://github.com/netdata/netdata/blob/master/docs/configure/secure-nodes.md) and [setting up replication](https://github.com/netdata/netdata/blob/master/streaming/README.md) are strongly recommended.
71
-
72
-
73
-## Install on Linux with one-line installer
74
-
75
-The **recommended** way to install Netdata on a Linux node (physical, virtual, container, IoT) is our one-line
76
-[kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
77
-This script automatically installs dependencies and builds Netdata from its source code.
78
-
79
-To install, copy the script, paste it into your node's terminal, and hit `Enter` to begin the installation process.
80
-
81
- <Tabs>
82
- <TabItem value="wget" label=<code>wget</code>>
83
-
84
- <OneLineInstallWget/>
85
-
86
- </TabItem>
87
- <TabItem value="curl" label=<code>curl</code>>
88
-
89
- <OneLineInstallCurl/>
90
-
91
- </TabItem>
92
-</Tabs>
93
-
94
-:::note
95
-If you plan to also claim the node to Netdata Cloud,
96
-make sure to replace `YOUR_CLAIM_TOKEN` with the claim token of your space,
97
-and `YOUR_ROOM_ID` with the ID of the room you are willing to claim to.
98
-You can leave the room id blank to have your node claimed to the default "All nodes" room.
99
-:::
100
-
101
-Jump down to [what's next](#whats-next) to learn how to view your new dashboard and take your next steps monitoring and
102
-troubleshooting with Netdata.
103
-
104
-## Other installation methods
105
-
106
-<InstallRegexLink>
107
- <InstallBoxRegexLink
108
- to="[](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md)"
109
- os="Run with Docker"
110
- svg="docker" />
111
- <InstallBoxRegexLink
112
- to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md)"
113
- os="Deploy on Kubernetes"
114
- svg="kubernetes" />
115
- <InstallBoxRegexLink
116
- to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md)"
117
- os="Install on macOS"
118
- svg="macos" />
119
- <InstallBoxRegexLink
120
- to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md)"
121
- os="Linux from Git"
122
- svg="linux" />
123
- <InstallBoxRegexLink
124
- to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/source.md)"
125
- os="Linux from source"
126
- svg="linux" />
127
- <InstallBoxRegexLink
128
- to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md)"
129
- os="Linux for offline nodes"
130
- svg="linux" />
131
-</InstallRegexLink>
132
-
133
-- [Run with Docker](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md)
134
-- [Deploy on Kubernetes](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md)
135
-- [Install on macOS](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md)
136
-- [Linux from Git](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md)
137
-- [Linux from source](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/source.md)
138
-- [Linux for offline nodes](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md)
139
-
140
-## Advanced installation options and troubleshooting
141
-
142
-### Automatic updates
143
-
144
-By default, Netdata's installation scripts enable automatic updates for both nightly and stable release channels.
145
-
146
-If you would prefer to update your Netdata agent manually, you can disable automatic updates by using the `--no-updates`
147
-option when you install or update Netdata using the [automatic one-line installation
148
-script](#automatic-one-line-installation-script).
149
-
150
-```bash
151
-wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/netdata-kickstart.sh --no-updates
152
-```
153
-
154
-With automatic updates disabled, you can choose exactly when and how you [update
155
-Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md).
156
-
157
-#### Network usage of Netdata’s automatic updater
158
-
159
-The auto-update functionality set up by the installation scripts requires working internet access to function
160
-correctly. In particular, it currently requires access to GitHub (to check if a newer version of the updater script
161
-is available or not, as well as potentially fetching build-time dependencies that are bundled as part of the install),
162
-and Google Cloud Storage (to check for newer versions of Netdata and download the sources if there is a newer version).
163
-
164
-Note that the auto-update functionality will check for updates to itself independently of updates to Netdata,
165
-and will try to use the latest version of the updater script whenever possible. This is intended to reduce the
166
-amount of effort required by users to get updates working again in the event of a bug in the updater code.
167
-
168
-### Nightly vs. stable releases
169
-
170
-The Netdata team maintains two releases of the Netdata agent: **nightly** and **stable**. By default, Netdata's
171
-installation scripts will give you **automatic, nightly** updates, as that is our recommended configuration.
172
-
173
-**Nightly**: We create nightly builds every 24 hours. They contain fully-tested code that fixes bugs or security flaws,
174
-or introduces new features to Netdata. Every nightly release is a candidate for then becoming a stable release—when
175
-we're ready, we simply change the release tags on GitHub. That means nightly releases are stable and proven to function
176
-correctly in the vast majority of Netdata use cases. That's why nightly is the _best choice for most Netdata users_.
177
-
178
-**Stable**: We create stable releases whenever we believe the code has reached a major milestone. Most often, stable
179
-releases correlate with the introduction of new, significant features. Stable releases might be a better choice for
180
-those who run Netdata in _mission-critical production systems_, as updates will come more infrequently, and only after
181
-the community helps fix any bugs that might have been introduced in previous releases.
182
-
183
-**Pros of using nightly releases:**
184
-
185
-- Get the latest features and bug fixes as soon as they're available
186
-- Receive security-related fixes immediately
187
-- Use stable, fully-tested code that's always improving
188
-- Leverage the same Netdata experience our community is using
189
-
190
-**Pros of using stable releases:**
191
-
192
-- Protect yourself from the rare instance when major bugs slip through our testing and negatively affect a Netdata
193
- installation
194
-- Retain more control over the Netdata version you use
195
-
196
-### Anonymous statistics
197
-
198
-Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self-hosted PostHog instance within the Netdata infrastructure. Read about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md) page.
199
-
200
-The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
201
-_actively_ contributing to Netdata's future.
202
-
203
-### Troubleshooting and known issues
204
-
205
-We are tracking a few issues related to installation and packaging.
206
-
207
-#### Older distributions (Ubuntu 14.04, Debian 8, CentOS 6) and OpenSSL
208
-
209
-If you're running an older Linux distribution or one that has reached EOL, such as Ubuntu 14.04 LTS, Debian 8, or CentOS
210
-6, your Agent may not be able to securely connect to Netdata Cloud due to an outdated version of OpenSSL. These old
211
-versions of OpenSSL cannot perform [hostname validation](https://wiki.openssl.org/index.php/Hostname_validation), which
212
-helps securely encrypt SSL connections.
213
-
214
-If you choose to continue using the outdated version of OpenSSL, your node will still connect to Netdata Cloud, albeit
215
-with hostname verification disabled. Without verification, your Netdata Cloud connection could be vulnerable to
216
-man-in-the-middle attacks.
217
-
218
-#### CentOS 6 and CentOS 8
219
-
220
-To install the Agent on certain CentOS and RHEL systems, you must enable non-default repositories, such as EPEL or
221
-PowerTools, to gather hard dependencies. See the [CentOS 6](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-6x) and
222
-[CentOS 8](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
223
-
224
-#### Access to file is not permitted
225
-
226
-If you see an error similar to `Access to file is not permitted: /usr/share/netdata/web//index.html` when you try to
227
-visit the Agent dashboard at `http://NODE:19999`, you need to update Netdata's permissions to match those of your
228
-system.
229
-
230
-Run `ls -la /usr/share/netdata/web/index.html` to find the file's permissions. You may need to change this path based on
231
-the error you're seeing in your browser. In the below example, the file is owned by the user `root` and the group
232
-`root`.
233
-
234
-```bash
235
-ls -la /usr/share/netdata/web/index.html
236
--rw-r--r--. 1 root root 89377 May 5 06:30 /usr/share/netdata/web/index.html
237
-```
238
-
239
-These files need to have the same user and group used to install your netdata. Suppose you installed netdata with user
240
-`netdata` and group `netdata`, in this scenario you will need to run the following command to fix the error:
241
-
242
-```bash
243
-# chown -R netdata.netdata /usr/share/netdata/web
244
-```
245
-
246
-#### Multiple versions of OpenSSL
247
-
248
-We've received reports from the community about issues with running the `kickstart.sh` script on systems that have both
249
-a distribution-installed version of OpenSSL and a manually-installed local version. The Agent's installer cannot handle
250
-both.
251
-
252
-#### Clang compiler on Linux
253
-
254
-Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the
255
-section on `nonrepresentable section on output`
256
-errors](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
257
-
258
-
packaging/installer/README.md
+118
-82
@@ -1,116 +1,145 @@
1
<!--
2
-title: "Installation guide"
3
-custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/installer/README.md
2
+title: "Install Netdata"
3
+description: "Download and install the open-source Netdata monitoring agent on physical/virtual servers, Linux (Ubuntu/Debian/CentOS/etc), Docker, Kubernetes, and many others, often with one command."
4
+sidebar_label: "Install Netdata"
5
+custom_edit_url: "https://github.com/netdata/netdata/edit/master/packaging/installer/README.md"
6
+learn_status: "Published"
7
+learn_topic_type: "Tasks"
8
+learn_rel_path: "Getting started"
9
-->
10
6
-import { Install, InstallBox } from '@site/src/components/Install/'
7
-
11
import { OneLineInstallWget, OneLineInstallCurl } from '@site/src/components/OneLineInstall/'
12
+import { InstallRegexLink, InstallBoxRegexLink } from '@site/src/components/InstallRegexLink/'
13
+import Tabs from '@theme/Tabs';
14
+import TabItem from '@theme/TabItem';
15
10
-# Installation guide
16
+## Get started
17
12
-Netdata is a monitoring agent designed to run on all your systems: physical and virtual servers, containers, even
13
-IoT/edge devices. Netdata runs on Linux, FreeBSD, macOS, Kubernetes, Docker, and all their derivatives.
18
+Netdata is a free and open-source (FOSS) monitoring agent that collects thousands of hardware and software metrics from
19
+any physical or virtual system (we call them _nodes_). These metrics are organized in an easy-to-use and -navigate interface.
20
15
-The best way to install Netdata is with our [**automatic one-line installation
16
-script**](#automatic-one-line-installation-script), which works with all Linux distributions and most macOS environments.
21
+Together with [Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx), you can monitor your entire infrastructure in
22
+real time and troubleshoot problems that threaten the health of your nodes.
23
18
-If you want to install Netdata with Docker, on a Kubernetes cluster, or a different operating system, see [Have a
19
-different operating system, or want to try another
20
-method?](#have-a-different-operating-system-or-want-to-try-another-method)
24
+Netdata runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT devices. It
25
+runs on Linux distributions (Ubuntu, Debian, CentOS, and more), container/microservice platforms (Kubernetes clusters,
26
+Docker), and many other operating systems (FreeBSD, macOS), with no `sudo` required.
27
22
-Some third parties, such as the packaging teams at various Linux distributions, distribute old, broken, or altered
23
-packages. We recommend you install Netdata using one of the methods listed below to guarantee you get the latest
24
-checksum-verified packages.
28
+To install Netdata in minutes on your platform:
29
26
-Netdata collects anonymous usage information by default and sends it to our self hosted [PostHog](https://github.com/PostHog/posthog) installation. PostHog is an open source product analytics platform, you can read
27
-about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md)
28
-page.
30
+1. Sign up to https://app.netdata.cloud/
31
+2. You will be presented with an empty space, and a prompt to "Connect Nodes" with the install command for each platform
32
+3. Select the platform you want to install Netdata to, copy and paste the script into your node's terminal, and run it
33
30
-The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
31
-_actively_ contributing to Netdata's future.
34
+Upon installation completing successfully, you should be able to see the node live in your Netdata Space and live charts in the Overview tab. [Read more about the cloud features](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx).
35
33
-## Automatic one-line installation script
36
+Where you go from here is based on your use case, immediate needs, and experience with monitoring and troubleshooting,
37
+but we have some hints on what you might want to do next.
38
35
- 
39
+### What's next?
40
37
-This method is fully automatic on all Linux distributions, including Ubuntu, Debian, Fedora, CentOS, and others, as well as on mac OS environments.
41
+Explore our [general advanced installation options and troubleshooting](#advanced-installation-options-and-troubleshooting), specific options for the [single line installer](#install-on-linux-with-one-line-installer), or [other installation methods](#other-installation-methods).
42
39
-To install Netdata, including all dependencies required to connect to Netdata Cloud, and get _automatic nightly
40
-updates_, run the following as your normal user:
43
+#### Agent user interface
44
42
-<OneLineInstallWget/>
45
+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
46
+the hostname/IP address of the remote node. You can also read more about [how the agent dashboard works](https://github.com/netdata/netdata/blob/master/docs/dashboard/how-dashboard-works.mdx), or dive directly into the many ways
47
+to [interact with charts](https://github.com/netdata/netdata/blob/master/docs/dashboard/interact-charts.mdx).
48
44
-Or, if you have cURL but not wget (such as on macOS):
49
+#### Configuration
50
46
-<OneLineInstallCurl/>
51
+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
52
+`edit-config` script, then apply that knowledge to mission-critical tweaks, such as [changing how long Netdata stores
53
+metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md).
54
48
-This script will preferentially use native DEB/RPM packages if we provide them for your platform.
55
+#### Data collection
56
50
-To see more information about this installation script, including how to disable automatic updates, get nightly vs.
51
-stable releases, or disable anonymous statistics, see the [`kickstart.sh` method
52
-page](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
57
+If Netdata didn't autodetect all the hardware, containers, services, or applications running on your node, you should
58
+learn more about [how data collectors work](https://github.com/netdata/netdata/blob/master/docs/collect/how-collectors-work.md). If there's a [supported
59
+collector](https://github.com/netdata/netdata/blob/master/collectors/COLLECTORS.md) for metrics you need, [configure the collector](https://github.com/netdata/netdata/blob/master/docs/collect/enable-configure.md)
60
+or read about its requirements to configure your endpoint to publish metrics in the correct format and endpoint.
61
54
-Scroll down for details about [automatic updates](#automatic-updates) or [nightly vs. stable
55
-releases](#nightly-vs-stable-releases).
62
+#### Alarms & notifications
63
57
-### Post-installation
64
+Netdata comes with hundreds of preconfigured alarms, designed by our monitoring gurus in parallel with our open-source
65
+community, but you may want to [edit alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/configure-alarms.md) or
66
+[enable notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) to customize your Netdata experience.
67
59
-When you're finished with installation, check out our [single-node](https://github.com/netdata/netdata/blob/master/docs/quickstart/single-node.md) or
60
-[infrastructure](https://github.com/netdata/netdata/blob/master/docs/quickstart/infrastructure.md) monitoring quickstart guides based on your use case.
68
+#### Make your deployment production ready
69
62
-Or, skip straight to [configuring the Netdata Agent](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md).
70
+Both [securing Netdata](https://github.com/netdata/netdata/blob/master/docs/configure/secure-nodes.md) and [setting up replication](https://github.com/netdata/netdata/blob/master/streaming/README.md) are strongly recommended.
71
64
-Read through Netdata's [documentation](https://learn.netdata.cloud/docs), which is structured based on actions and
65
-solutions, to enable features like health monitoring, alarm notifications, long-term metrics storage, exporting to
66
-external databases, and more.
72
68
-## Have a different operating system, or want to try another method?
73
+## Install on Linux with one-line installer
74
70
-Netdata works on many different platforms. To see all supported platforms, check out our [platform support
71
-policy](https://github.com/netdata/netdata/blob/master/packaging/PLATFORM_SUPPORT.md).
75
+The **recommended** way to install Netdata on a Linux node (physical, virtual, container, IoT) is our one-line
76
+[kickstart script](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md).
77
+This script automatically installs dependencies and builds Netdata from its source code.
78
73
-Below, you can find a few additional installation methods, followed by separate instructions for a variety of unique
74
-operating systems.
79
+To install, copy the script, paste it into your node's terminal, and hit `Enter` to begin the installation process.
80
76
-### Alternative methods
81
+ <Tabs>
82
+ <TabItem value="wget" label=<code>wget</code>>
83
78
-<Install>
79
- <InstallBox
80
- to="/docs/agent/packaging/installer/methods/kickstart"
81
- os="General Linux with one-line installer (recommended)"
82
- svg="linux" />
83
- <InstallBox
84
- to="/docs/agent/packaging/installer/methods/packages"
85
- os="Native DEB/RPM packages for Linux"
86
- svg="linux" />
87
- <InstallBox
88
- to="/docs/agent/packaging/docker"
89
- os="Run with Docker"
84
+ <OneLineInstallWget/>
85
+
86
+ </TabItem>
87
+ <TabItem value="curl" label=<code>curl</code>>
88
+
89
+ <OneLineInstallCurl/>
90
+
91
+ </TabItem>
92
+</Tabs>
93
+
94
+:::note
95
+If you plan to also claim the node to Netdata Cloud,
96
+make sure to replace `YOUR_CLAIM_TOKEN` with the claim token of your space,
97
+and `YOUR_ROOM_ID` with the ID of the room you are willing to claim to.
98
+You can leave the room id blank to have your node claimed to the default "All nodes" room.
99
+:::
100
+
101
+Jump down to [what's next](#whats-next) to learn how to view your new dashboard and take your next steps monitoring and
102
+troubleshooting with Netdata.
103
+
104
+## Other installation methods
105
+
106
+<InstallRegexLink>
107
+ <InstallBoxRegexLink
108
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md)"
109
+ os="Run with Docker"
110
svg="docker" />
91
- <InstallBox
92
- to="/docs/agent/packaging/installer/methods/kubernetes"
93
- os="Deploy on Kubernetes"
111
+ <InstallBoxRegexLink
112
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md)"
113
+ os="Deploy on Kubernetes"
114
svg="kubernetes" />
95
- <InstallBox
96
- to="/docs/agent/packaging/installer/methods/macos"
97
- os="Install on macOS"
115
+ <InstallBoxRegexLink
116
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md)"
117
+ os="Install on macOS"
118
svg="macos" />
99
- <InstallBox
100
- to="/docs/agent/packaging/installer/methods/manual"
101
- os="Linux from Git"
119
+ <InstallBoxRegexLink
120
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md)"
121
+ os="Linux from Git"
122
svg="linux" />
103
- <InstallBox
104
- to="/docs/agent/packaging/installer/methods/source"
123
+ <InstallBoxRegexLink
124
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/source.md)"
125
os="Linux from source"
126
svg="linux" />
107
- <InstallBox
108
- to="/docs/agent/packaging/installer/methods/offline"
127
+ <InstallBoxRegexLink
128
+ to="[](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md)"
129
os="Linux for offline nodes"
130
svg="linux" />
111
-</Install>
131
+</InstallRegexLink>
132
+
133
+- [Run with Docker](https://github.com/netdata/netdata/blob/master/packaging/docker/README.md)
134
+- [Deploy on Kubernetes](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kubernetes.md)
135
+- [Install on macOS](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/macos.md)
136
+- [Linux from Git](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md)
137
+- [Linux from source](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/source.md)
138
+- [Linux for offline nodes](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/offline.md)
139
113
-## Automatic updates
140
+## Advanced installation options and troubleshooting
141
+
142
+### Automatic updates
143
144
By default, Netdata's installation scripts enable automatic updates for both nightly and stable release channels.
145
@@ -125,7 +154,7 @@ wget -O /tmp/netdata-kickstart.sh https://my-netdata.io/kickstart.sh && sh /tmp/
154
With automatic updates disabled, you can choose exactly when and how you [update
155
Netdata](https://github.com/netdata/netdata/blob/master/packaging/installer/UPDATE.md).
156
128
-### Network usage of Netdata’s automatic updater
157
+#### Network usage of Netdata’s automatic updater
158
159
The auto-update functionality set up by the installation scripts requires working internet access to function
160
correctly. In particular, it currently requires access to GitHub (to check if a newer version of the updater script
@@ -136,7 +165,7 @@ Note that the auto-update functionality will check for updates to itself indepen
165
and will try to use the latest version of the updater script whenever possible. This is intended to reduce the
166
amount of effort required by users to get updates working again in the event of a bug in the updater code.
167
139
-## Nightly vs. stable releases
168
+### Nightly vs. stable releases
169
170
The Netdata team maintains two releases of the Netdata agent: **nightly** and **stable**. By default, Netdata's
171
installation scripts will give you **automatic, nightly** updates, as that is our recommended configuration.
@@ -164,11 +193,18 @@ the community helps fix any bugs that might have been introduced in previous rel
193
installation
194
- Retain more control over the Netdata version you use
195
167
-## Troubleshooting and known issues
196
+### Anonymous statistics
197
+
198
+Starting with v1.30, Netdata collects anonymous usage information by default and sends it to a self-hosted PostHog instance within the Netdata infrastructure. Read about the information collected, and learn how to-opt, on our [anonymous statistics](https://github.com/netdata/netdata/blob/master/docs/anonymous-statistics.md) page.
199
+
200
+The usage statistics are _vital_ for us, as we use them to discover bugs and prioritize new features. We thank you for
201
+_actively_ contributing to Netdata's future.
202
+
203
+### Troubleshooting and known issues
204
205
We are tracking a few issues related to installation and packaging.
206
171
-### Older distributions (Ubuntu 14.04, Debian 8, CentOS 6) and OpenSSL
207
+#### Older distributions (Ubuntu 14.04, Debian 8, CentOS 6) and OpenSSL
208
209
If you're running an older Linux distribution or one that has reached EOL, such as Ubuntu 14.04 LTS, Debian 8, or CentOS
210
6, your Agent may not be able to securely connect to Netdata Cloud due to an outdated version of OpenSSL. These old
@@ -179,13 +215,13 @@ If you choose to continue using the outdated version of OpenSSL, your node will
215
with hostname verification disabled. Without verification, your Netdata Cloud connection could be vulnerable to
216
man-in-the-middle attacks.
217
182
-### CentOS 6 and CentOS 8
218
+#### CentOS 6 and CentOS 8
219
220
To install the Agent on certain CentOS and RHEL systems, you must enable non-default repositories, such as EPEL or
221
PowerTools, to gather hard dependencies. See the [CentOS 6](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-6x) and
222
[CentOS 8](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#centos--rhel-8x) sections for more information.
223
188
-### Access to file is not permitted
224
+#### Access to file is not permitted
225
226
If you see an error similar to `Access to file is not permitted: /usr/share/netdata/web//index.html` when you try to
227
visit the Agent dashboard at `http://NODE:19999`, you need to update Netdata's permissions to match those of your
@@ -207,13 +243,13 @@ These files need to have the same user and group used to install your netdata. S
243
# chown -R netdata.netdata /usr/share/netdata/web
244
```
245
210
-### Multiple versions of OpenSSL
246
+#### Multiple versions of OpenSSL
247
248
We've received reports from the community about issues with running the `kickstart.sh` script on systems that have both
249
a distribution-installed version of OpenSSL and a manually-installed local version. The Agent's installer cannot handle
250
both.
251
216
-### Clang compiler on Linux
252
+#### Clang compiler on Linux
253
254
Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the
255
section on `nonrepresentable section on output`