summaryrefslogtreecommitdiffstats
path: root/docs/observability-centralization-points/metrics-centralization-points
diff options
context:
space:
mode:
Diffstat (limited to 'docs/observability-centralization-points/metrics-centralization-points')
-rw-r--r--docs/observability-centralization-points/metrics-centralization-points/README.md2
-rw-r--r--docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md2
-rw-r--r--docs/observability-centralization-points/metrics-centralization-points/configuration.md8
-rw-r--r--docs/observability-centralization-points/metrics-centralization-points/faq.md4
-rw-r--r--docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md2
5 files changed, 9 insertions, 9 deletions
diff --git a/docs/observability-centralization-points/metrics-centralization-points/README.md b/docs/observability-centralization-points/metrics-centralization-points/README.md
index 0efdacd41..812b493d7 100644
--- a/docs/observability-centralization-points/metrics-centralization-points/README.md
+++ b/docs/observability-centralization-points/metrics-centralization-points/README.md
@@ -45,4 +45,4 @@ A Cluster is configured as a number of circular **Proxies**, ie. each of the nod
## Best Practices
-Refer to [Best Practices for Observability Centralization Points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/best-practices.md).
+Refer to [Best Practices for Observability Centralization Points](/docs/observability-centralization-points/best-practices.md).
diff --git a/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md b/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md
index d2202960f..17a10b02e 100644
--- a/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md
+++ b/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md
@@ -28,7 +28,7 @@ Netdata Children need to maintain a retention only for the time required to swit
## Restoring a Netdata Parent after maintenance
-Given the [replication limitations](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/replication-of-past-samples.md#replication-limitations), special care is needed when restoring a Netdata Parent after some long maintenance work on it.
+Given the [replication limitations](/docs/observability-centralization-points/metrics-centralization-points/replication-of-past-samples.md#replication-limitations), special care is needed when restoring a Netdata Parent after some long maintenance work on it.
If the Netdata Children do not have enough retention to replicate the missing data on this Netdata Parent, it is preferable to block access to this Netdata Parent from the Netdata Children, until it replicates the missing data from the other Netdata Parents.
diff --git a/docs/observability-centralization-points/metrics-centralization-points/configuration.md b/docs/observability-centralization-points/metrics-centralization-points/configuration.md
index e52f7309f..bf2aa98db 100644
--- a/docs/observability-centralization-points/metrics-centralization-points/configuration.md
+++ b/docs/observability-centralization-points/metrics-centralization-points/configuration.md
@@ -28,7 +28,7 @@ To enable the reception of metrics from Netdata Children, generate a random API
uuidgen
```
-Then, copy the UUID generated, [edit `stream.conf`](#edit-stream.conf), find the section that reads like the following and replace `API_KEY` with the UUID you generated:
+Then, copy the UUID generated, [edit `stream.conf`](#edit-streamconf), find the section that reads like the following and replace `API_KEY` with the UUID you generated:
```ini
[API_KEY]
@@ -40,7 +40,7 @@ Save the file and restart Netdata.
## Configuring Netdata Children
-To enable streaming metrics to a Netdata Parent, [edit `stream.conf`](#edit-stream.conf), and at the `[stream]` section at the top, set:
+To enable streaming metrics to a Netdata Parent, [edit `stream.conf`](#edit-streamconf), and at the `[stream]` section at the top, set:
```ini
[stream]
@@ -61,11 +61,11 @@ While encrypting the connection between your parent and child nodes is recommend
This example uses self-signed certificates.
> **Note**
-> This section assumes you have read the documentation on [how to edit the Netdata configuration files](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration.md).
+> This section assumes you have read the documentation on [how to edit the Netdata configuration files](/docs/netdata-agent/configuration/README.md).
<!-- here we need link to the section that will contain the restarting instructions -->
1. **Parent node**
- To generate an SSL key and certificate using `openssl`, take a look at the related section around [Securing Netdata Agents](https://github.com/netdata/netdata/blob/master/src/web/server/README.md#enable-httpstls-support) in our Documentation.
+ To generate an SSL key and certificate using `openssl`, take a look at the related section around [Securing Netdata Agents](/src/web/server/README.md#enable-httpstls-support) in our Documentation.
2. **Child node**
Update `stream.conf` to enable SSL/TLS and allow self-signed certificates. Append ':SSL' to the destination and uncomment 'ssl skip certificate verification'.
diff --git a/docs/observability-centralization-points/metrics-centralization-points/faq.md b/docs/observability-centralization-points/metrics-centralization-points/faq.md
index 3c019108c..027dfc748 100644
--- a/docs/observability-centralization-points/metrics-centralization-points/faq.md
+++ b/docs/observability-centralization-points/metrics-centralization-points/faq.md
@@ -4,7 +4,7 @@
Netdata Parents generally scale well. According [to our tests](https://blog.netdata.cloud/netdata-vs-prometheus-performance-analysis/) Netdata Parents scale better than Prometheus for the same workload: -35% CPU utilization, -49% Memory Consumption, -12% Network Bandwidth, -98% Disk I/O, -75% Disk footprint.
-For more information, Check [Sizing Netdata Parents](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md).
+For more information, Check [Sizing Netdata Parents](/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md).
## If I set up a parents cluster, will I be able to have more Child nodes stream to them?
@@ -43,7 +43,7 @@ Yes. Function requests will be received by the Parents and forwarded to the Chil
## If I have a cluster of parents and get one out for maintenance for a few hours, will it have missing data when it returns back online?
-Check [Restoring a Netdata Parent after maintenance](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md).
+Check [Restoring a Netdata Parent after maintenance](/docs/observability-centralization-points/metrics-centralization-points/clustering-and-high-availability-of-netdata-parents.md).
## I have a cluster of parents. Which one is used by Netdata Cloud?
diff --git a/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md b/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md
index 79b223348..edfbabe93 100644
--- a/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md
+++ b/docs/observability-centralization-points/metrics-centralization-points/sizing-netdata-parents.md
@@ -1,3 +1,3 @@
# Sizing Netdata Parents
-To estimate CPU, RAM, and disk requirements for your Netdata Parents, check [sizing Netdata agents](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/sizing-netdata-agents/README.md).
+To estimate CPU, RAM, and disk requirements for your Netdata Parents, check [sizing Netdata agents](/docs/netdata-agent/sizing-netdata-agents/README.md).