summaryrefslogtreecommitdiffstats
path: root/docs/guides
diff options
context:
space:
mode:
authorHugo Valente <82235632+hugovalente-pm@users.noreply.github.com>2021-08-09 12:49:40 +0100
committerGitHub <noreply@github.com>2021-08-09 14:49:40 +0300
commitffd4c9219493a392c5c0992ce1e6d00bc62585d0 (patch)
treeeae4efa93fe552635d0f51c381118463ee394bcc /docs/guides
parent8293d5ff56873c2ae33c7b7903ebbcfd9756d3f2 (diff)
changed the term claim to connect (to Cloud) on docs (#11378)
Diffstat (limited to 'docs/guides')
-rw-r--r--docs/guides/deploy/ansible.md8
-rw-r--r--docs/guides/monitor/anomaly-detection.md2
-rw-r--r--docs/guides/monitor/kubernetes-k8s-netdata.md8
-rw-r--r--docs/guides/monitor/lamp-stack.md2
-rw-r--r--docs/guides/step-by-step/step-03.md4
-rw-r--r--docs/guides/troubleshoot/monitor-debug-applications-ebpf.md4
6 files changed, 14 insertions, 14 deletions
diff --git a/docs/guides/deploy/ansible.md b/docs/guides/deploy/ansible.md
index b1afdf3158..3e7c64a561 100644
--- a/docs/guides/deploy/ansible.md
+++ b/docs/guides/deploy/ansible.md
@@ -33,7 +33,7 @@ operate. When you deploy Netdata with Ansible, you're also deploying _monitoring
In this guide, we'll walk through the process of using an [Ansible
playbook](https://github.com/netdata/community/tree/main/netdata-agent-deployment/ansible-quickstart) to automatically
-deploy the Netdata Agent to any number of distributed nodes, manage the configuration of each node, and claim them to
+deploy the Netdata Agent to any number of distributed nodes, manage the configuration of each node, and connect them to
your Netdata Cloud account. You'll go from some unmonitored nodes to a infrastructure monitoring solution in a matter of
minutes.
@@ -98,7 +98,7 @@ two different SSH keys supplied by AWS.
### Edit the `vars/main.yml` file
-In order to claim your node(s) to your Space in Netdata Cloud, and see all their metrics in real-time in [composite
+In order to connect your node(s) to your Space in Netdata Cloud, and see all their metrics in real-time in [composite
charts](/docs/visualize/overview-infrastructure.md) or perform [Metric
Correlations](https://learn.netdata.cloud/docs/cloud/insights/metric-correlations), you need to set the `claim_token`
and `claim_room` variables.
@@ -120,7 +120,7 @@ claim_rooms: XXXXX
Change the `dbengine_multihost_disk_space` if you want to change the metrics retention policy by allocating more or less
disk space for storing metrics. The default is 2048 Mib, or 2 GiB.
-Because we're claiming this node to Netdata Cloud, and will view its dashboards there instead of via the IP address or
+Because we're connecting this node to Netdata Cloud, and will view its dashboards there instead of via the IP address or
hostname of the node, the playbook disables that local dashboard by setting `web_mode` to `none`. This gives a small
security boost by not allowing any unwanted access to the local dashboard.
@@ -147,7 +147,7 @@ Next, Ansible makes changes to each node according to the `tasks` defined in the
[returns](https://docs.ansible.com/ansible/latest/reference_appendices/common_return_values.html#changed) whether each
task results in a changed, failure, or was skipped entirely.
-The task to install Netdata will take a few minutes per node, so be patient! Once the playbook reaches the claiming
+The task to install Netdata will take a few minutes per node, so be patient! Once the playbook reaches the connect to Cloud
task, your nodes start populating your Space in Netdata Cloud.
## What's next?
diff --git a/docs/guides/monitor/anomaly-detection.md b/docs/guides/monitor/anomaly-detection.md
index f680f5f2ef..1b224b9705 100644
--- a/docs/guides/monitor/anomaly-detection.md
+++ b/docs/guides/monitor/anomaly-detection.md
@@ -23,7 +23,7 @@ library](https://github.com/yzhao062/pyod/tree/master), which periodically runs
quantify how anomalous certain charts are.
All these metrics and alarms are available for centralized monitoring in [Netdata Cloud](https://app.netdata.cloud). If
-you choose to sign up for Netdata Cloud and [claim your nodes](/claim/README.md), you will have the ability to run
+you choose to sign up for Netdata Cloud and [coonect your nodes](/claim/README.md), you will have the ability to run
tailored anomaly detection on every node in your infrastructure, regardless of its purpose or workload.
In this guide, you'll learn how to set up the anomalies collector to instantly detect anomalies in an Nginx web server
diff --git a/docs/guides/monitor/kubernetes-k8s-netdata.md b/docs/guides/monitor/kubernetes-k8s-netdata.md
index c5cb2c1bc9..5d4886e682 100644
--- a/docs/guides/monitor/kubernetes-k8s-netdata.md
+++ b/docs/guides/monitor/kubernetes-k8s-netdata.md
@@ -45,9 +45,9 @@ To follow this tutorial, you need:
- A free Netdata Cloud account. [Sign up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) if you don't have one
already.
-- A working cluster running Kubernetes v1.9 or newer, with a Netdata deployment and claimed parent/child nodes. See
+- A working cluster running Kubernetes v1.9 or newer, with a Netdata deployment and connected parent/child nodes. See
our [Kubernetes deployment process](/packaging/installer/methods/kubernetes.md) for details on deployment and
- claiming.
+ conneting to Cloud.
- The [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/) command line tool, within [one minor version
difference](https://kubernetes.io/docs/tasks/tools/install-kubectl/#before-you-begin) of your cluster, on an
administrative system.
@@ -98,10 +98,10 @@ robot-shop web-8bb887476-lkcjx 1/1 Running 0 14m
## Explore Netdata's Kubernetes monitoring charts
The Netdata Helm chart deploys and enables everything you need for monitoring Kubernetes on every layer. Once you deploy
-Netdata and claim your cluster's nodes, you're ready to check out the visualizations **with zero configuration**.
+Netdata and connect your cluster's nodes, you're ready to check out the visualizations **with zero configuration**.
To get started, [sign in](https://app.netdata.cloud/sign-in?cloudRoute=/spaces) to your Netdata Cloud account. Head over
-to the War Room you claimed your cluster to, if not **General**.
+to the War Room you connected your cluster to, if not **General**.
Netdata Cloud is already visualizing your Kubernetes metrics, streamed in real-time from each node, in the
[Overview](https://learn.netdata.cloud/docs/cloud/visualize/overview):
diff --git a/docs/guides/monitor/lamp-stack.md b/docs/guides/monitor/lamp-stack.md
index 95aa03f0bb..38b9d0bef3 100644
--- a/docs/guides/monitor/lamp-stack.md
+++ b/docs/guides/monitor/lamp-stack.md
@@ -167,7 +167,7 @@ If the Netdata Agent isn't already open in your browser, open a new tab and navi
> If you [signed up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) for Netdata Cloud earlier, you can also view
> the exact same LAMP stack metrics there, plus additional features, like drag-and-drop custom dashboards. Be sure to
-> [claim your node](/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
+> [connecting your node](/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
Netdata automatically organizes all metrics and charts onto a single page for easy navigation. Peek at gauges to see
overall system performance, then scroll down to see more. Click-and-drag with your mouse to pan _all_ charts back and
diff --git a/docs/guides/step-by-step/step-03.md b/docs/guides/step-by-step/step-03.md
index 2319adb449..a2f37beebf 100644
--- a/docs/guides/step-by-step/step-03.md
+++ b/docs/guides/step-by-step/step-03.md
@@ -43,7 +43,7 @@ features, new collectors for more applications, and improved UI, so will Cloud.
## Get started with Netdata Cloud
-Signing in, onboarding, and claiming your first nodes only takes a few minutes, and we have a [Get started with
+Signing in, onboarding, and connecting your first nodes only takes a few minutes, and we have a [Get started with
Cloud](https://learn.netdata.cloud/docs/cloud/get-started) guide to help you walk through every step.
Or, if you're feeling confident, dive right in.
@@ -82,7 +82,7 @@ nodes](https://user-images.githubusercontent.com/1153921/80831018-e158ac80-8b9e-
## What's next?
-Now that you have a Netdata Cloud account with a claimed node (or a few!) and can navigate between your dashboards with
+Now that you have a Netdata Cloud account with a connected node (or a few!) and can navigate between your dashboards with
Visited nodes, it's time to learn more about how you can configure Netdata to your liking. From there, you'll be able to
customize your Netdata experience to your exact infrastructure and the information you need.
diff --git a/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md b/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
index d6c4b06976..688e7d296b 100644
--- a/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
+++ b/docs/guides/troubleshoot/monitor-debug-applications-ebpf.md
@@ -236,8 +236,8 @@ same application on multiple systems and want to correlate how it performs on ea
findings with someone else on your team.
If you don't already have a Netdata Cloud account, go [sign in](https://app.netdata.cloud) and get started for free.
-Read the [get started with Cloud guide](https://learn.netdata.cloud/docs/cloud/get-started) for a walkthrough of node
-claiming and other fundamentals.
+Read the [get started with Cloud guide](https://learn.netdata.cloud/docs/cloud/get-started) for a walkthrough of
+connecting nodes to and other fundamentals.
Once you've added one or more nodes to a Space in Netdata Cloud, you can see aggregated eBPF metrics in the [Overview
dashboard](/docs/visualize/overview-infrastructure.md) under the same **Applications** or **eBPF** sections that you