@cryptotaxi247 / netdata-1 / commits / 51f811ccf

Replace `/docs` links with GitHub links (#14796)

* Update REFERENCE.md * replace redirected links * replace /docs links with their absolute GitHub link counterparts

Fotis Voutsas committed Mar 23, 2023 at 20:46 UTC 51f811ccf8da5a472fa522fe2569f903cf394724
4 files changed +5 -5
docs/cloud/insights/metric-correlations.md
+1 -1
@@ -53,7 +53,7 @@ Behind the scenes, Netdata will aggregate the raw data as needed such that arbit
53
54 ### Data
55
56 -Netdata is different from typical observability agents since, in addition to just collecting raw metric values, it will by default also assign an "[Anomaly Bit](/docs/agent/ml#anomaly-bit)" related to each collected metric each second. This bit will be 0 for "normal" and 1 for "anomalous". This means that each metric also natively has an "[Anomaly Rate](/docs/agent/ml#anomaly-rate)" associated with it and, as such, MC can be run against the raw metric values or their corresponding anomaly rates.
56 +Netdata is different from typical observability agents since, in addition to just collecting raw metric values, it will by default also assign an "[Anomaly Bit](https://github.com/netdata/netdata/tree/master/ml#anomaly-bit---100--anomalous-0--normal)" related to each collected metric each second. This bit will be 0 for "normal" and 1 for "anomalous". This means that each metric also natively has an "[Anomaly Rate](https://github.com/netdata/netdata/tree/master/ml#anomaly-rate---averageanomaly-bit)" associated with it and, as such, MC can be run against the raw metric values or their corresponding anomaly rates.
57
58 **Note**: Read more [here](https://github.com/netdata/netdata/blob/master/ml/README.md) to learn more about the native anomaly detection features within netdata.
59
docs/cloud/visualize/dashboards.md
+2 -2
@@ -27,7 +27,7 @@ dashboards](https://user-images.githubusercontent.com/1153921/108529360-a2145d00
27 In the modal, give your new dashboard a name, and click **+ Add**.
28
29 Click the **Add Chart** button to add your first chart card. From the dropdown, select either *All Nodes** or a specific
30 -node. If you select **All Nodes**, you will add a [composite chart](/docs/cloud/visualize/overview#composite-charts) to
30 +node. If you select **All Nodes**, you will add a [composite chart](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md) to
31 your new dashboard. Next, select the context. You'll see a preview of the chart before you finish adding it.
32
33 The **Add Text** button creates a new card with user-defined text, which you can use to describe or document a
@@ -46,7 +46,7 @@ of any number of **cards**, which can contain charts or text.
46 ### Chart cards
47
48 Click the **Add Chart** button to add your first chart card. From the dropdown, select either *All Nodes** or a specific
49 -node. If you select **All Nodes**, you will add a [composite chart](/docs/cloud/visualize/overview#composite-charts) to
49 +node. If you select **All Nodes**, you will add a [composite chart](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/overview.md) to
50 your new dashboard. Next, select the context. You'll see a preview of the chart before you finish adding it.
51
52 The charts you add to any dashboard are fully interactive, just like the charts in an Agent dashboard or a single node's
docs/cloud/visualize/interact-new-charts.md
+1 -1
@@ -193,7 +193,7 @@ following:
193 :::
194
195 For more details on each, you can refer to our Agent's HTTP API details
196 -on [Data Queries - Data Grouping](/docs/agent/web/api/queries#data-grouping).
196 +on [Data Queries - Data Grouping](https://github.com/netdata/netdata/blob/master/web/api/queries/README.md#data-grouping).
197
198 ### Reset to defaults
199
docs/cloud/visualize/nodes.md
+1 -1
@@ -35,5 +35,5 @@ need to configure those nodes to collect from additional data sources. See our [
35 to learn how to use dozens of pre-installed collectors that can instantly collect from your favorite services and applications.
36
37 If you want to see up to 30 days of historical metrics in Cloud (and more on individual node dashboards), read about [changing how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md). Also, see our
38 -[calculator](/docs/store/change-metrics-storage#calculate-the-system-resources-RAM-disk-space-needed-to-store-metrics)
38 +[calculator](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
39 for finding the disk and RAM you need to store metrics for a certain period of time.