Update documentation (#15606)
Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
Kamil Kieliszczyk committed
Jul 28, 2023 at 11:26 UTC
ea23a946ec377ec64ed4e7877d41a94f2613f1d6
3 files changed
+6
-6
docs/category-overview-pages/deployment-strategies.md
+2
-2
@@ -49,7 +49,7 @@ An Agent connected to a Parent is called a _Child_. It will _stream_ metrics to
49
50
When using Cloud, it is recommended that just the Parent is connected to Cloud. Child Agents can then be configured to have short retention, in RAM instead of on Disk, and have alerting and other features disabled. Because they don't need to connect to Cloud themselves, those children can then be further secured by not allowing outbound traffic.
51
52
-
52
+
53
54
This setup allows for leaner Child nodes and is good for setups with more than a handful of nodes. Metrics data remains accessible if the Child node is temporarily unavailable or decommissioned, although there is no failover in case the Parent becomes unavailable.
55
@@ -60,7 +60,7 @@ For high availability, Parents can be configured to stream data for their childr
60
61
With both Parent Agents connected to Cloud, Cloud will route queries to either Parent transparently, depending on their availability. Alerts trigger on either Parent will stream to Cloud, and Cloud will deduplicate and debounce state changes to prevent spurious notifications.
62
63
-
63
+
64
65
66
## Configuration Details
packaging/installer/README.md
+3
-3
@@ -88,7 +88,7 @@ To install, copy the script, paste it into your node's terminal, and hit `Enter`
88
> If you plan to also claim the node to Netdata Cloud, make sure to replace `YOUR_CLAIM_TOKEN` with the claim token of your space, and `YOUR_ROOM_ID` with the ID of the room you are claiming to.
89
> You can leave the room id blank to have your node claimed to the default "All nodes" room.
90
91
-Jump down to [what's next](#whats-next) to learn how to view your new dashboard and take your next steps monitoring and
91
+Jump up to [what's next](#whats-next) to learn how to view your new dashboard and take your next steps in monitoring and
92
troubleshooting with Netdata.
93
94
## Other installation methods
@@ -221,7 +221,7 @@ PowerTools, to gather hard dependencies. See the [CentOS 6](https://github.com/n
221
222
#### Access to file is not permitted
223
224
-If you see an error similar to `Access to file is not permitted: /usr/share/netdata/web//index.html` when you try to
224
+If you see an error similar to `Access to file is not permitted: /usr/share/netdata/web/index.html` when you try to
225
visit the Agent dashboard at `http://NODE:19999`, you need to update Netdata's permissions to match those of your
226
system.
227
@@ -238,7 +238,7 @@ These files need to have the same user and group used to install your netdata. S
238
`netdata` and group `netdata`, in this scenario you will need to run the following command to fix the error:
239
240
```bash
241
-# chown -R netdata.netdata /usr/share/netdata/web
241
+# chown -R netdata:netdata /usr/share/netdata/web
242
```
243
244
#### Multiple versions of OpenSSL
packaging/installer/methods/kickstart.md
+1
-1
@@ -104,7 +104,7 @@ The `kickstart.sh` script accepts a number of optional parameters to control how
104
The following options are mutually exclusive and specifiy special operations other than trying to install Netdata normally or update an existing install:
105
106
- `--reinstall`: If there is an existing install, reinstall it instead of trying to update it. If there is not an existing install, install netdata normally.
107
-- `--reinstall-even-if-unsafe`: If there is an existing install, reinstall it instead of trying to update it, even if doing so is known to potentially break things (for example, if we cannot detect what tyep of installation it is). If there is not an existing install, install Netdata normally.
107
+- `--reinstall-even-if-unsafe`: If there is an existing install, reinstall it instead of trying to update it, even if doing so is known to potentially break things (for example, if we cannot detect what type of installation it is). If there is not an existing install, install Netdata normally.
108
- `--reinstall-clean`: If there is an existing install, uninstall it before trying to install Netdata. Fails if there is no existing install.
109
- `--uninstall`: Uninstall an existing installation of Netdata. Fails if there is no existing install.
110
- `--claim-only`: If there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.