mirror of
https://github.com/netdata/netdata.git
synced 2025-04-06 22:38:55 +00:00
Docs: Remove old Cloud/dashboard and replace with new Cloud/dashboard (#8874)
* Add options to daemon, clean up claiming * Caught one more old conf * Remove cloud docs * I did a lot of things * Rewrite tutorial step 3 * Remove my nodes menu, sync what-is-netdata * Restore ACLK/claim/daemon docs to be handled by docs-go-live * Fix up what-is-netdata * More cleanup of README/what-is-netdata * Restore daemon/config/README.md * Fix frontmatter * Change title, fix broken link * Copyediting fixes * Remove symbols * Add a few more GIFs * Fix hash * Fix other hash * Fix wording in web gui * Address Andrew's and Jacek's comments
This commit is contained in:
Joel Hans
GitHub
parent
4609d5b3dd
commit
9d712b5135
16 changed files with 279 additions and 851 deletions
DOCUMENTATION.mdREADME.md
daemon/config
docs
packaging/installer
web
|
|
@ -1,87 +0,0 @@
|
|||
# Netdata Documentation
|
||||
|
||||
**Netdata is real-time health monitoring and performance troubleshooting for systems and applications.** It helps you
|
||||
instantly diagnose slowdowns and anomalies in your infrastructure with thousands of metrics, interactive visualizations,
|
||||
and insightful health alarms. Plus, long-term storage comes ready out-of-the-box, so can collect, monitor, and maintain
|
||||
your metrics in one insightful place.
|
||||
|
||||
## Navigating the Netdata documentation
|
||||
|
||||
Welcome! You've arrived at the documentation for Netdata. Use the links below to find answers to the most common
|
||||
questions about Netdata, such as how to install it, getting started guides, basic configuration, and adding more charts.
|
||||
Or, explore all of Netdata's documentation using the table of contents to your left.
|
||||
|
||||
<div class="homepage-nav">
|
||||
<a class="nav-page" href="packaging/installer/">
|
||||
<div class="button-header">
|
||||
<h3>Installation guide</h3>
|
||||
<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 448 512" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg"><path d="M224.3 273l-136 136c-9.4 9.4-24.6 9.4-33.9 0l-22.6-22.6c-9.4-9.4-9.4-24.6 0-33.9l96.4-96.4-96.4-96.4c-9.4-9.4-9.4-24.6 0-33.9L54.3 103c9.4-9.4 24.6-9.4 33.9 0l136 136c9.5 9.4 9.5 24.6.1 34zm192-34l-136-136c-9.4-9.4-24.6-9.4-33.9 0l-22.6 22.6c-9.4 9.4-9.4 24.6 0 33.9l96.4 96.4-96.4 96.4c-9.4 9.4-9.4 24.6 0 33.9l22.6 22.6c9.4 9.4 24.6 9.4 33.9 0l136-136c9.4-9.2 9.4-24.4 0-33.8z"></path></svg>
|
||||
</div>
|
||||
<div class="button-text">
|
||||
<p>Use our automated one-line installation script to install Netdata on Linux systems or find detailed instructions for binary packages, Kubernetes, Docker, macOS, and more.</p>
|
||||
</div>
|
||||
</a>
|
||||
<a class="nav-page" href="docs/step-by-step/step-00/">
|
||||
<div class="button-header">
|
||||
<h3>Step-by-step tutorial</h3>
|
||||
<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 448 512" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg"><path d="M224.3 273l-136 136c-9.4 9.4-24.6 9.4-33.9 0l-22.6-22.6c-9.4-9.4-9.4-24.6 0-33.9l96.4-96.4-96.4-96.4c-9.4-9.4-9.4-24.6 0-33.9L54.3 103c9.4-9.4 24.6-9.4 33.9 0l136 136c9.5 9.4 9.5 24.6.1 34zm192-34l-136-136c-9.4-9.4-24.6-9.4-33.9 0l-22.6 22.6c-9.4 9.4-9.4 24.6 0 33.9l96.4 96.4-96.4 96.4c-9.4 9.4-9.4 24.6 0 33.9l22.6 22.6c9.4 9.4 24.6 9.4 33.9 0l136-136c9.4-9.2 9.4-24.4 0-33.8z"></path></svg>
|
||||
</div>
|
||||
<div class="button-text">
|
||||
<p>Take a guided tour through each of Netdata's core features—perfect for beginners. Follow detailed instructions to monitor your systems and apps, and start your journey into performance troubleshooting.</p>
|
||||
</div>
|
||||
</a>
|
||||
<a class="nav-page" href="docs/getting-started/">
|
||||
<div class="button-header">
|
||||
<h3>Getting started guide</h3>
|
||||
<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 448 512" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg"><path d="M224.3 273l-136 136c-9.4 9.4-24.6 9.4-33.9 0l-22.6-22.6c-9.4-9.4-9.4-24.6 0-33.9l96.4-96.4-96.4-96.4c-9.4-9.4-9.4-24.6 0-33.9L54.3 103c9.4-9.4 24.6-9.4 33.9 0l136 136c9.5 9.4 9.5 24.6.1 34zm192-34l-136-136c-9.4-9.4-24.6-9.4-33.9 0l-22.6 22.6c-9.4 9.4-9.4 24.6 0 33.9l96.4 96.4-96.4 96.4c-9.4 9.4-9.4 24.6 0 33.9l22.6 22.6c9.4 9.4 24.6 9.4 33.9 0l136-136c9.4-9.2 9.4-24.4 0-33.8z"></path></svg>
|
||||
</div>
|
||||
<div class="button-text">
|
||||
<p>Have some monitoring and system administration experience? Dive right into configuring Netdata, accessing the dashboard, working with the daemon, and changing how Netdata stores metrics.</p>
|
||||
</div>
|
||||
</a>
|
||||
<a class="nav-page" href="docs/configuration-guide/">
|
||||
<div class="button-header">
|
||||
<h3>Configuration guide</h3>
|
||||
<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 448 512" height="1em" width="1em" xmlns="http://www.w3.org/2000/svg"><path d="M224.3 273l-136 136c-9.4 9.4-24.6 9.4-33.9 0l-22.6-22.6c-9.4-9.4-9.4-24.6 0-33.9l96.4-96.4-96.4-96.4c-9.4-9.4-9.4-24.6 0-33.9L54.3 103c9.4-9.4 24.6-9.4 33.9 0l136 136c9.5 9.4 9.5 24.6.1 34zm192-34l-136-136c-9.4-9.4-24.6-9.4-33.9 0l-22.6 22.6c-9.4 9.4-9.4 24.6 0 33.9l96.4 96.4-96.4 96.4c-9.4 9.4-9.4 24.6 0 33.9l22.6 22.6c9.4 9.4 24.6 9.4 33.9 0l136-136c9.4-9.2 9.4-24.4 0-33.8z"></path></svg>
|
||||
</div>
|
||||
<div class="button-text">
|
||||
<p>Take your configuration options from the <em>getting started guide</em> to the next level. Increase metrics retention, modify how charts are displayed, disable collectors, and modify alarms.</p>
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
**Netdata Cloud**: Use [Netdata Cloud](docs/netdata-cloud/) and the [Nodes View](docs/netdata-cloud/nodes-view.md) to
|
||||
view real-time, distributed health monitoring and performance troubleshooting data for all your systems in one place.
|
||||
Add as many nodes as you'd like!
|
||||
|
||||
**Advanced users**: For those who already understand how to access a Netdata dashboard and perform basic configuration,
|
||||
feel free to see what's behind any of these other doors.
|
||||
|
||||
- [Tutorial: Change how long Netdata stores metrics](docs/tutorials/longer-metrics-storage.md): Extend Netdata's
|
||||
long-term metrics storage database by allowing Netdata to use more of your system's RAM and disk.
|
||||
- [Netdata Behind Nginx](docs/Running-behind-nginx.md): Use an Nginx web server instead of Netdata's built-in server
|
||||
to enable TLS, HTTPS, and basic authentication.
|
||||
- [Collect more metrics](collectors/README.md) from other services and applications: Enable new internal
|
||||
or external plugins and understand when auto-detection works.
|
||||
- [Performance](docs/Performance.md): Tips on running Netdata on devices with limited CPU and RAM resources, such as
|
||||
embedded devices, IoT, and edge devices.
|
||||
- [Streaming](streaming/): Information for those who want to centralize Netdata metrics from any number of distributed
|
||||
agents.
|
||||
- [Backends](backends/): Learn how to archive Netdata's real-time metrics to a time series database (like Prometheus)
|
||||
for long-term archiving.
|
||||
|
||||
Visit the [contributing guide](CONTRIBUTING.md), [contributing to documentation
|
||||
guide](docs/contributing/contributing-documentation.md), and [documentation style
|
||||
guide](docs/contributing/style-guide.md) to learn more about our community and how you can get started contributing to
|
||||
Netdata.
|
||||
|
||||
**Want to get news, how-tos, and heaps of monitoring savvy straight from Netdata? Subscribe to our newsletter to monitor
|
||||
our team of monitoring pros.**
|
||||
|
||||
<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/shell.js"></script>
|
||||
<script>
|
||||
hbspt.forms.create({
|
||||
portalId: "4567453",
|
||||
formId: "6a20deb5-a1e6-4312-9c4d-f6862f947fe0"
|
||||
});
|
||||
</script>
|
||||
28
README.md
28
README.md
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
---
|
||||
title: "Netdata"
|
||||
date: 2020-04-06
|
||||
date: 2020-05-01
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/README.md
|
||||
---
|
||||
-->
|
||||
|
|
@ -72,7 +72,7 @@ Netdata!](https://img.shields.io/twitter/url/http/shields.io.svg?style=social&la
|
|||
The following animated GIF shows the top part of a typical Netdata dashboard.
|
||||
|
||||
|
||||
action](https://user-images.githubusercontent.com/1153921/80827388-b9fee100-8b98-11ea-8f60-0d7824667cd3.gif)
|
||||
|
||||
> A typical Netdata dashboard, in 1:1 timing. Charts can be panned by dragging them, zoomed in/out with `SHIFT` + `mouse
|
||||
> wheel`, an area can be selected for zoom-in with `SHIFT` + `mouse selection`. Netdata is highly interactive,
|
||||
|
|
@ -175,7 +175,7 @@ For more information about running Netdata in Docker, check the [docker installa
|
|||
|
||||
From Netdata v1.12 and above, anonymous usage information is collected by default and sent to Google Analytics. To read
|
||||
more about the information collected and how to opt-out, check the [anonymous statistics
|
||||
page](docs/anonymous-statistics.md).
|
||||
page](/docs/anonymous-statistics.md).
|
||||
|
||||
## Why Netdata
|
||||
|
||||
|
|
@ -304,8 +304,8 @@ This is what you should expect from Netdata:
|
|||
[flock.com](/health/notifications/flock/), [hangouts](/health/notifications/hangouts/),
|
||||
[irc](/health/notifications/irc/), [kavenegar.com](/health/notifications/kavenegar/),
|
||||
[messagebird.com](/health/notifications/messagebird/), [pagerduty.com](/health/notifications/pagerduty/),
|
||||
[prowl](health/notifications/prowl/), [pushbullet.com](/health/notifications/pushbullet/),
|
||||
[pushover.net](health/notifications/pushover/), [rocket.chat](/health/notifications/rocketchat/),
|
||||
[prowl](/health/notifications/prowl/), [pushbullet.com](/health/notifications/pushbullet/),
|
||||
[pushover.net](/health/notifications/pushover/), [rocket.chat](/health/notifications/rocketchat/),
|
||||
[slack.com](/health/notifications/slack/), [smstools3](/health/notifications/smstools3/),
|
||||
[syslog](/health/notifications/syslog/), [telegram.org](/health/notifications/telegram/),
|
||||
[twilio.com](/health/notifications/twilio/), [web](/health/notifications/web/) and [custom
|
||||
|
|
@ -337,7 +337,8 @@ This is what you should expect from Netdata:
|
|||
To improve clarity on charts, Netdata dashboards present **positive** values for metrics representing `read`, `input`,
|
||||
`inbound`, `received` and **negative** values for metrics representing `write`, `output`, `outbound`, `sent`.
|
||||
|
||||
|
||||
|
||||
|
||||
_Netdata charts showing the bandwidth and packets of a network interface. `received` is positive and `sent` is
|
||||
negative._
|
||||
|
|
@ -346,7 +347,8 @@ negative._
|
|||
|
||||
Netdata charts automatically zoom vertically, to visualize the variation of each metric within the visible time-frame.
|
||||
|
||||
|
||||
|
||||
|
||||
_A zero-based `stacked` chart, automatically switches to an auto-scaled `area` chart when a single dimension is
|
||||
selected._
|
||||
|
|
@ -356,27 +358,23 @@ selected._
|
|||
Charts on Netdata dashboards are synchronized to each other. There is no master chart. Any chart can be panned or zoomed
|
||||
at any time, and all other charts will follow.
|
||||
|
||||
|
||||
|
||||
|
||||
_Charts are panned by dragging them with the mouse. Charts can be zoomed in/out with`SHIFT` + `mouse wheel` while the
|
||||
mouse pointer is over a chart._
|
||||
|
||||
> The visible time-frame (pan and zoom) is propagated from Netdata server to Netdata server when navigating via the
|
||||
> [My nodes menu](/registry/README.md).
|
||||
|
||||
### Highlighted time-frame
|
||||
|
||||
To improve visual anomaly detection across charts, the user can highlight a time-frame (by pressing `Alt` + `mouse
|
||||
selection`) on all charts.
|
||||
|
||||
|
||||
|
||||
|
||||
_A highlighted time-frame can be given by pressing `Alt` + `mouse selection` on any chart. Netdata will highlight the
|
||||
same range on all charts._
|
||||
|
||||
> Highlighted ranges are propagated from Netdata server to Netdata server, when navigating via the [My nodes
|
||||
> menu](/registry/README.md).
|
||||
|
||||
## What Netdata monitors
|
||||
|
||||
Netdata can collect metrics from 200+ popular services and applications, on top of dozens of system-related metrics
|
||||
|
|
|
|||
|
|
@ -161,7 +161,7 @@ In this area of `netdata.conf` you can find configuration options for individual
|
|||
following the pattern `[NAME]`.
|
||||
|
||||
Using the settings and values under these sections, you can control all aspects of a specific chart. You can change its
|
||||
title, make it appear higher in Netdata's [menu](/web/gui/README.md#menus), tweak its dimensions, and much more.
|
||||
title, make it appear higher in Netdata's [menu](/web/gui/README.md#metrics-menus), tweak its dimensions, and much more.
|
||||
|
||||
To find the name of a given chart, and thus the name of its section in `netdata.conf`, look at the top-left corner of a
|
||||
chart:
|
||||
|
|
@ -178,7 +178,7 @@ that is information about lines that begin with `dim`, which affect a chart's di
|
|||
| `enabled` | A boolean (`yes` or `no`) that explicitly enables or disables the chart in question. |
|
||||
| `cache directory` | The directory where cache files for this plugin, if needed, are stored. |
|
||||
| `chart type` | Defines what type of chart to display. It can be `line`, `area`, or `stacked`. If empty or missing, `line` will be used. |
|
||||
| `type` | Uniquely identify which [menu](/web/gui/README.md#menus) on the Netdata dashboard this chart should appear under. Some examples include `system` (**System**), `disk` (**Disks**), `net` (**Network Interfaces**), and `netdata` (**Netdata Monitoring**). |
|
||||
| `type` | Uniquely identify which [metrics menu](/web/gui/README.md#metrics-menus) on the Netdata dashboard this chart should appear under. Some examples include `system` (**System**), `disk` (**Disks**), `net` (**Network Interfaces**), and `netdata` (**Netdata Monitoring**). |
|
||||
| `family` | Change the chart's [family](/web/README.md#families) from its default. For example, you could force a disk space chart to collect metrics for family `sdb` instead of family `sda`. |
|
||||
| `units` | Text for the label of the vertical axis of the chart. This means all dimensions should have the same unit of measurement. |
|
||||
| `context` | Change the default [context](/web/README.md#contexts) of the chart. Changing this setting will affect what metrics and metrics the chart displays, and which alarms are attached to it. |
|
||||
|
|
|
|||
79
docs/agent-cloud.md
Normal file
79
docs/agent-cloud.md
Normal file
|
|
@ -0,0 +1,79 @@
|
|||
<!--
|
||||
---
|
||||
title: "Use the Agent with Netdata Cloud"
|
||||
date: 2020-05-04
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/agent-cloud.md
|
||||
---
|
||||
-->
|
||||
|
||||
# Use the Agent with Netdata Cloud
|
||||
|
||||
While the Netdata Agent is an enormously powerful _distributed_ health monitoring and performance troubleshooting tool,
|
||||
many of its users need to monitor dozens or hundreds of systems at the same time. That's why we built Netdata Cloud, a
|
||||
hosted web interface that gives you real-time visibility into your entire infrastructure.
|
||||
|
||||
There are two main ways to use your Agent(s) with Netdata Cloud. You can use both these methods simultaneously, or just
|
||||
one, based on your needs:
|
||||
|
||||
- Use Netdata Cloud's web interface for monitoring an entire infrastructure, with any number of Agents, in one
|
||||
centralized dashboard.
|
||||
- Use **Visited nodes** to quickly navigate between the dashboards of nodes you've recently visited.
|
||||
|
||||
## Monitor an infrastructure with Netdata Cloud
|
||||
|
||||
We designed Netdata Cloud to help you see health and performance metrics, plus active alarms, in a single interface.
|
||||
Here's what a small infrastructure might look like:
|
||||
|
||||
|
||||
|
||||
[Read more about Netdata Cloud](https://learn.netdata.cloud/docs/cloud/) to better understand how it gives you real-time
|
||||
visibility into your entire infrastructure, and why you might consider using it.
|
||||
|
||||
Next, [get started in 5 minutes](https://learn.netdata.cloud/docs/cloud/get-started/), or read our [claiming
|
||||
reference](/claim/README.md) for a complete investigation of Cloud's security and encryption features, plus instructions
|
||||
for Docker containers.
|
||||
|
||||
## Navigate between dashboards with Visited nodes
|
||||
|
||||
If you don't want to use Netdata Cloud's web interface, you can still connect multiple nodes through the **Visited
|
||||
nodes** menu, which appears on the left-hand side of the dashboard.
|
||||
|
||||
You can use the Visited nodes menu to navigate between the dashboards of many different Agent-monitored systems quickly.
|
||||
|
||||
To add nodes to your Visited nodes menu, you first need to navigate to that node's dashboard, then click the **Sign in**
|
||||
button at the top of the dashboard. On the screen that appears, which states your node is requesting access to your
|
||||
Netdata Cloud account, sign in with your preferred method.
|
||||
|
||||
Cloud redirects you back to your node's dashboard, which is now connected to your Netdata Cloud account. You can now see
|
||||
the Visited nodes menu, which is populated by a single node.
|
||||
|
||||
|
||||
|
||||
If you previously went through the Cloud onboarding process to create a Space and War Room, you will also see these in
|
||||
the Visited Nodes menu. You can click on your Space or any of your War Rooms to navigate to Netdata Cloud and continue
|
||||
monitoring your infrastructure from there.
|
||||
|
||||
|
||||
|
||||
To add more Agents to your Visited nodes menu, visit them and sign in again. This process connects that node to your
|
||||
Cloud account and further populates the menu.
|
||||
|
||||
Once you've added more than one node, you can use the menu to switch between various dashboards without remembering IP
|
||||
addresses or hostnames or saving bookmarks for every node you want to monitor.
|
||||
|
||||
|
||||
|
||||
## What's next?
|
||||
|
||||
The Agent-Cloud integration is highly adaptable to the needs of any infrastructure or user. If you want to learn more
|
||||
about how you might want to use or configure Cloud, we recommend the following:
|
||||
|
||||
- Get an overview of Cloud's features by reading [Cloud documentation](https://learn.netdata.cloud/docs/cloud/).
|
||||
- Follow the 5-minute [get started with Cloud](https://learn.netdata.cloud/docs/cloud/get-started/) guide to finish
|
||||
onboarding and claim your first nodes.
|
||||
- Better understand how agents connect securely to the Cloud with [claiming](/claim/README.md) and [Agent-Cloud
|
||||
link](/aclk/README.md) documentation.
|
||||
|
|
@ -1,17 +1,17 @@
|
|||
<!--
|
||||
---
|
||||
title: "Getting started guide"
|
||||
date: 2020-04-06
|
||||
title: "Get started guide"
|
||||
date: 2020-05-04
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/getting-started.md
|
||||
---
|
||||
-->
|
||||
|
||||
# Getting started guide
|
||||
# Get started guide
|
||||
|
||||
Thanks for trying Netdata! In this getting started guide, we'll quickly walk you through the first steps you should take
|
||||
after getting Netdata installed.
|
||||
Thanks for trying the Netdata Agent! In this getting started guide, we'll quickly walk you through the first steps you
|
||||
should take after installing the Agent.
|
||||
|
||||
Netdata can collect thousands of metrics in real-time and use its database for long-term metrics storage without any
|
||||
The Agent can collect thousands of metrics in real-time and use its database for long-term metrics storage without any
|
||||
configuration, but there are some valuable things to know to get the most out of Netdata based on your needs.
|
||||
|
||||
We'll skip right into some technical details, so if you're brand-new to monitoring the health and performance of systems
|
||||
|
|
@ -22,14 +22,11 @@ and applications, our [**step-by-step tutorial**](/docs/step-by-step/step-00.md)
|
|||
|
||||
## Access the dashboard
|
||||
|
||||
Open up your web browser of choice and navigate to `http://YOUR-HOST:19999`. Welcome to Netdata!
|
||||
Open up your web browser of choice and navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname
|
||||
of your Agent. Hit **Enter**. Welcome to Netdata!
|
||||
|
||||
|
||||
|
||||
<details markdown="1"><summary>Want to see the dashboard and its features in action? Check out our video.</summary>
|
||||
<iframe width="720" height="405" src="https://www.youtube.com/embed/Ob6-Wkb6ZBA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
</details>
|
||||
dashboard](https://user-images.githubusercontent.com/1153921/80825153-abaec600-8b94-11ea-8b17-1b770a2abaa9.gif)
|
||||
|
||||
**What's next?**:
|
||||
|
||||
|
|
@ -97,9 +94,9 @@ Some modules, like `chrony`, are disabled by default and must be enabled manuall
|
|||
|
||||
Once Netdata detects a valid source of data, it will continue trying to collect data from it. For example, if
|
||||
Netdata is collecting data from an Nginx web server, and you shut Nginx down, Netdata will collect new data as soon as
|
||||
you start the web server back up—no restart necessary.
|
||||
you start the web server back up—no restart necessary.
|
||||
|
||||
### Configuring plugins
|
||||
### Configure plugins
|
||||
|
||||
Even if Netdata auto-detects your service/application, you might want to configure what, or how often, Netdata is
|
||||
collecting data.
|
||||
|
|
@ -192,29 +189,33 @@ Find the `SEND_EMAIL="YES"` line and change it to `SEND_EMAIL="NO"`.
|
|||
- See all the alarm options via the [health configuration reference](/health/REFERENCE.md).
|
||||
- Add a new notification method, like [Slack](/health/notifications/slack/).
|
||||
|
||||
## Monitoring multiple systems with Netdata
|
||||
## Monitor multiple systems with Netdata Cloud
|
||||
|
||||
If you have Netdata installed on multiple systems, you can have them all appear in the **My nodes** menu at the top-left
|
||||
corner of the dashboard.
|
||||
If you have the Agent installed on multiple nodes, you can use Netdata Cloud in two ways: Monitor the health and
|
||||
performance of an entire infrastructure via the Cloud web interface, or use the Visited Nodes menu that's built into
|
||||
every dashboard.
|
||||
|
||||
To show all your servers in that menu, you need to [register for or sign in](/docs/netdata-cloud/signing-in.md) to
|
||||
[Netdata Cloud](/docs/netdata-cloud/README.md) from each system. Each system will then appear in the **My nodes** menu, which you
|
||||
can use to navigate between your systems quickly.
|
||||
For example, a small infrastructure monitored via Netdata Cloud:
|
||||
|
||||
|
||||
|
||||
|
||||
Whenever you pan, zoom, highlight, select, or pause a chart, Netdata will synchronize those settings with any other
|
||||
agent you visit via the My nodes menu. Even your scroll position is synchronized, so you'll see the same charts and
|
||||
respective data for easy comparisons or root cause analysis.
|
||||
And the process of using the Visited nodes menu to move between Agent dashboards running on various systems, both local
|
||||
and remote:
|
||||
|
||||
You can now seamlessly track performance anomalies across your entire infrastructure!
|
||||
|
||||
|
||||
You can use these features together or separately—the decision is up to you and the needs of your infrastructure.
|
||||
|
||||
**What's next?**:
|
||||
|
||||
- Read up on how the [Netdata Cloud registry works](/registry/), and what kind of data it stores and sends to
|
||||
your web browser.
|
||||
- Familiarize yourself with the [Nodes View](/docs/netdata-cloud/nodes-view.md)
|
||||
- Read about the [Agent-Cloud integration]().
|
||||
- Get an overview of Cloud's features by reading [Cloud documentation](https://learn.netdata.cloud/docs/cloud/).
|
||||
- Follow the 5-minute [get started with Cloud](https://learn.netdata.cloud/docs/cloud/get-started/) guide to finish
|
||||
onboarding and claim your first nodes.
|
||||
- Better understand how agents connect securely to the Cloud with [claiming](/claim/README.md) and [Agent-Cloud
|
||||
link](/aclk/README.md) documentation.
|
||||
|
||||
## Start, stop, and restart Netdata
|
||||
|
||||
|
|
@ -235,7 +236,8 @@ and `init.d`:
|
|||
## What's next?
|
||||
|
||||
Even after you've configured `netdata.conf`, tweaked alarms, learned the basics of performance troubleshooting, and
|
||||
added all your systems to the **My nodes** menu, you've just gotten started with Netdata.
|
||||
claimed all your systems in Netdata Cloud or added them to the Visited nodes menu, you've just gotten started with
|
||||
Netdata.
|
||||
|
||||
Take a look at some more advanced features and configurations:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,55 +0,0 @@
|
|||
<!--
|
||||
---
|
||||
title: "Netdata Cloud"
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/netdata-cloud/README.md
|
||||
---
|
||||
-->
|
||||
|
||||
# Netdata Cloud
|
||||
|
||||
Netdata Cloud is core to our ongoing mission to provide real-time, distributed health monitoring and performance troubleshooting. It's the foundation of an ecosystem of tools that will help you build more extraordinary infrastructures.
|
||||
|
||||
Netdata Cloud is also the next iteration of our global Netdata registry. For technical information about how our registries work, what information they store, and how your web browser "talks" to both, visit our [registry documentation](/registry/README.md).
|
||||
|
||||
Learn more about the future of Netdata Cloud on our [announcement post](https://blog.netdata.cloud/posts/netdata-cloud-announcement/).
|
||||
|
||||
## Registering for or signing in to Netdata Cloud
|
||||
|
||||
**If you're ready to register for a new Netdata Cloud account, or sign in to your existing Netdata Cloud account, visit our [signing in guide](/docs/netdata-cloud/signing-in.md) for details.**
|
||||
|
||||
> If you're running a private registry and are interested in trying out Netdata Cloud as a replacement for your private
|
||||
> registry, read [our notice](/docs/netdata-cloud/signing-in.md#private-registries-and-netdata-cloud) about
|
||||
> transitioning from a private registry to our Netdata Cloud registry.
|
||||
|
||||
## Netdata Cloud features
|
||||
|
||||
Netdata Cloud currently enables two features: the **My nodes** in the top-left corner of the Netdata dashboard, and the
|
||||
[**Nodes View**](/docs/netdata-cloud/nodes-view.md).
|
||||
|
||||
We have an aggressive roadmap of new features, such as Workspaces for different parts of your infrastructure, Rooms to collaborate with colleagues, and the ability to receive alarms from any number of distributed Netdata agents in a single place. Read more about our proposed features [here](https://blog.netdata.cloud/posts/netdata-cloud-announcement/#what-features-will-netdata-cloud-offer).
|
||||
|
||||
### Planned enterprise features (paid)
|
||||
|
||||
Large enterprises have unique real-time monitoring needs. They have thousands of servers and applications running concurrently, and are willing to pay for the complex features that help them make smarter, faster decisions about their infrastructure. We expect to create a paid tier of Netdata Cloud with a recurring, per-user pricing model that will unlock enterprise-focused features.
|
||||
|
||||
A few of these planned features include:
|
||||
|
||||
- Long-term storage of Netdata UI snapshots
|
||||
- Active Directory integration for single sign-on
|
||||
- Private service status pages
|
||||
- Extended retention of alarms timelines
|
||||
- Incident response toolkits
|
||||
- Additional enterprise plugins and integrations
|
||||
- Extended retention of chat messages
|
||||
|
||||
Again, we expect that the vast majority of Netdata's users won't need these features. Creating these two tiers will help us further fund the company's efforts to deploy Netdata's open-source agent on a massive scale and entirely for free.
|
||||
|
||||
## Running Netdata without Netdata Cloud
|
||||
|
||||
Netdata Cloud is entirely optional. The application will never force you to create a Netdata Cloud account or associate nodes with the public registries. But, if you choose not to use Netdata Cloud, you will be missing out on the [Nodes View](/docs/netdata-cloud/nodes-view.md) and other upcoming features.
|
||||
|
||||
## Running Netdata Cloud on-premises or as a hosted instance
|
||||
|
||||
We plan on making both on-premises and hosted instances of Netdata Cloud available to enterprises. Until then, we are creating a list of people and businesses interested in either of these options. To add yourself or your organization to this list, email us at [info@netdata.cloud](mailto:info@netdata.cloud).
|
||||
|
||||
[](<>)
|
||||
|
|
@ -1,215 +0,0 @@
|
|||
<!--
|
||||
---
|
||||
title: "Using the Nodes View"
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/netdata-cloud/nodes-view.md
|
||||
---
|
||||
-->
|
||||
|
||||
# Using the Nodes View
|
||||
|
||||
## Introduction
|
||||
|
||||
As of v1.15.0 of Netdata, and in conjunction with our announcement post about the [future of Netdata](https://blog.netdata.cloud/posts/netdata-cloud-announcement/), we have enabled an entirely new way to view your infrastructure using the open-source Netdata agent in conjunction with Netdata Cloud: the **Nodes View**.
|
||||
|
||||
This view, powered by Netdata Cloud, provides an aggregated view of the Netdata agents that you have associated with your Netdata Cloud account. The main benefit of Nodes View is seeing the health of your infrastructure from a single interface, especially if you have many systems running Netdata. With Nodes View, you can monitor the health status of your nodes via active alarms and view a subset of real-time performance metrics the agent is collecting every second.
|
||||
|
||||
!!! attention "Nodes View is beta software!"
|
||||
The Nodes View is currently in beta, so all typical warnings about beta software apply. You may come across bugs or inconsistencies.
|
||||
|
||||
```
|
||||
The current version of Nodes uses the API available on each Netdata agent to check for new alarms and the machine's overall health/availability. In the future, we will offer both polling via the API and real-time streaming of health status/metrics.
|
||||
```
|
||||
|
||||
## The Nodes View
|
||||
|
||||
To access the Nodes View, you must first be signed in to Netdata Cloud. To register for an account, or sign in to an existing account, visit our [signing in guide](signing-in.md) for details.
|
||||
|
||||
Once you're signed in to Netdata Cloud, clicking on any of the **Nodes Beta** buttons in the node's web dashboard will lead you to the Nodes View. Find one (`1`) in the dropdown menu in the upper-right corner, a second (`2`) in the top navigation bar, and a third (`3`) in the dropdown menu in the top-left corner of the Netdata dashboard.
|
||||
|
||||
|
||||
|
||||
### Nodes
|
||||
|
||||
The primary component of the Nodes View is a list of all the nodes with Netdata agents you have associated with your Netdata Cloud account via the Netdata Cloud registry.
|
||||
|
||||
|
||||
|
||||
Depending on which [view mode](#view-modes) you're using, Nodes View will present you with information about that node, such as its hostname, operating system, warnings/critical alerts, and any [supported services](#Services-available-in-the-Nodes-View) that are running on that node. Here is an example of the **full** view mode:
|
||||
|
||||
|
||||
|
||||
The background color of each Node entry is an indication of its health status:
|
||||
|
||||
| Health status | Background color |
|
||||
| ------------- | ------------------------------------------------------------------------------------------------- |
|
||||
| **White** | Normal status, no alarms |
|
||||
| **Yellow** | 1 or more active warnings |
|
||||
| **Red** | 1 or more active critical alerts |
|
||||
| **Grey** | Node is unreachable (server unreachable [due to network conditions], server down, or changed URL) |
|
||||
|
||||
### Node overview
|
||||
|
||||
When you click on any of the Nodes, an overview sidebar will appear on the right-hand side of the Nodes View.
|
||||
|
||||
This overview contains the following:
|
||||
|
||||
- An icon (`1`) representing the operating system installed on that machine
|
||||
- The hostname (`2`) of the machine
|
||||
- A link (`3`) to the URL at which the web dashboard is available
|
||||
- Three tabs (`4`) for **System** metrics, **Services** metrics, and **Alarms**
|
||||
- A number of selectors (`5`) to choose which metrics/alarms are shown in the overview
|
||||
- **System** tab: _Overview_, _Disks_, and _Network_ selectors
|
||||
- **Services** tab: _Databases_, _Web_, and _Messaging_ selectors
|
||||
- **Alarms** tab: _Critical_ and _Warning_ selectors
|
||||
- The visualizations and/or alarms (`6`) supported under the chosen tab and selector
|
||||
- Any other available URLS (`7`) associated with that node under the **Node URLs** header.
|
||||
|
||||
|
||||
|
||||
By default, clicking on a Node will display the sidebar with the **System** tab enabled. If there are warnings or alarms active for that Node, the **Alarms** tab will be displayed by default.
|
||||
|
||||
**The visualizations in the overview sidebar are live!** As with all of Netdata's visualizations, you can scrub forward and backward in time, zoom, pause, and pinpoint anomalies down to the second.
|
||||
|
||||
#### System tab
|
||||
|
||||
The **System** tab has three sections: *Overview*, *Disks*, and *Network*.
|
||||
|
||||
_Overview_ displays visualizations for `CPU`, `System Load Average` `Disk I/O`, `System RAM`, `System Swap`, `Physical Network Interfaces Aggregated Bandwidth`, and the URL of the node.
|
||||
|
||||
_Disks_ displays visualizations for `Disk Utilization Time`, and `Disk Space Usage` for every available disk.
|
||||
|
||||
_Network_ displays visualizations for `Bandwidth` for every available networking device.
|
||||
|
||||
#### Services tab
|
||||
|
||||
The **Services** tab will show visualizations for any [supported services](#Services-available-in-the-Nodes-View) that are running on that node. Three selectors are available: _Databases_, _Web_, and _Messaging_. If there are no services under any of these categories, the selector will not be clickable.
|
||||
|
||||
#### Alarms tab
|
||||
|
||||
The **Alarms** tab contains two selectors: _Critical_ and _Warning_. If there are no alarms under either of these categories, the selector will not be clickable.
|
||||
|
||||
Both of these tabs will display alarms information when available, along with the relevant visualization with metrics from your Netdata agent. The `view` link redirects you to the web dashboard for the selected node and automatically shows the appropriate visualization and timeframe.
|
||||
|
||||
|
||||
|
||||
### Filtering field
|
||||
|
||||
The search field will be useful for Netdata Cloud users with dozens or hundreds of Nodes. You can filter for the hostname of the Node you're interested in, the operating system it's running, or even for the services installed.
|
||||
|
||||
The filtering field will offer you autocomplete suggestions. For example, the options available after typing `ng` into the filtering field:
|
||||
|
||||
|
||||
|
||||
If you select multiple filters, results will display according to an `OR` operator.
|
||||
|
||||
### View modes
|
||||
|
||||
To the right of the filtering field is three functions that will help you organize your Visited Nodes according to your preferences.
|
||||
|
||||
|
||||
|
||||
The view mode button lets you switch between three view modes:
|
||||
|
||||
- **Full** mode, which displays the following information in a large squares for each connected Node:
|
||||
- Operating system
|
||||
- Critical/warning alerts in two separate indicators
|
||||
- Hostname
|
||||
- Icons for [supported services](#services-available-in-the-nodes-view)
|
||||
|
||||
|
||||
|
||||
- **Compact** mode, which displays the following information in small squares for each connected Node:
|
||||
- Operating system
|
||||
|
||||
|
||||
|
||||
- **Detailed** mode, which displays the following information in large horizontal rectangles for each connected Node:
|
||||
- Operating system
|
||||
- Critical/warning alerts in two separate indicators
|
||||
- Hostname
|
||||
- Icons for [supported services](#services-available-in-the-nodes-view)
|
||||
|
||||
|
||||
|
||||
## Sorting, and grouping
|
||||
|
||||
The **Sort by** dropdown allows you to choose between sorting _alphabetically by hostname_, most _recently-viewed_ nodes, and most _frequently-view_ nodes.
|
||||
|
||||
The **Group by** dropdown lets you switch between _alarm status_, _running services_, or _online status_.
|
||||
|
||||
For example, the following screenshot represents the Nodes list with the following options: _detailed list_, _frequently visited_, and _alarm status_.
|
||||
|
||||
|
||||
|
||||
Play around with the options until you find a setup that works for you.
|
||||
|
||||
## Adding more agents to the Nodes View
|
||||
|
||||
There is currently only one way to associate additional Netdata nodes with your Netdata Cloud account. You must visit the web dashboard for each node and click the **Sign in** button and complete the [sign in process](signing-in.md#signing-in-to-your-netdata-cloud-account).
|
||||
|
||||
!!! note ""
|
||||
We are aware that the process of registering each node individually is cumbersome for those who want to implement Netdata Cloud's features across a large infrastructure.
|
||||
|
||||
```
|
||||
Please view [this comment on issue #6318](https://github.com/netdata/netdata/issues/6318#issuecomment-504106329) for how we plan on improving the process for adding additional nodes to your Netdata Cloud account.
|
||||
```
|
||||
|
||||
## Services available in the Nodes View
|
||||
|
||||
The following tables elaborate on which services will appear in the Nodes View. Alerts from [other collectors](/collectors/README.md), when entered an alarm status, will show up in the _Alarms_ tab despite not appearing in the
|
||||
|
||||
### Databases
|
||||
|
||||
These services will appear under the _Databases_ selector beneath the _Services_ tab.
|
||||
|
||||
| Service | Collectors | Context #1 | Context #2 | Context #3 |
|
||||
|--- |--- |--- |--- |--- |
|
||||
| MySQL | `python.d.plugin:mysql`, `go.d.plugin:mysql` | `mysql.queries` | `mysql.net` | `mysql.connections` |
|
||||
| MariaDB | `python.d.plugin:mysql`, `go.d.plugin:mysql` | `mysql.queries` | `mysql.net` | `mysql.connections` |
|
||||
| Oracle Database | `python.d.plugin:oracledb` | `oracledb.session_count` | `oracledb.physical_disk_read_writes ` | `oracledb.tablespace_usage_in_percent` |
|
||||
| PostgreSQL | `python.d.plugin:postgres` | `postgres.checkpointer` | `postgres.archive_wal` | `postgres.db_size` |
|
||||
| MongoDB | `python.d.plugin:mongodb` | `mongodb.active_clients` | `mongodb.read_operations` | `mongodb.write_operations` |
|
||||
| ElasticSearch | `python.d.plugin:elasticsearch` | `elastic.search_performance_total` | `elastic.index_performance_total` | `elastic.index_segments_memory` |
|
||||
| CouchDB | `python.d.plugin:couchdb` | `couchdb.activity` | `couchdb.response_codes` | |
|
||||
| Proxy SQL | `python.d.plugin:proxysql` | `proxysql.questions` | `proxysql.pool_status` | `proxysql.pool_overall_net` |
|
||||
| Redis | `python.d.plugin:redis` | `redis.operations` | `redis.net` | `redis.connections` |
|
||||
| MemCached | `python.d.plugin:memcached` | `memcached.cache` | `memcached.net` | `memcached.connections` |
|
||||
| RethinkDB | `python.d.plugin:rethinkdbs` | `rethinkdb.cluster_queries` | `rethinkdb.cluster_clients_active` | `rethinkdb.cluster_connected_servers` |
|
||||
| Solr | `go.d.plugin:solr` | `solr.search_requests` | `solr.update_requests` | |
|
||||
|
||||
### Web services
|
||||
|
||||
These services will appear under the _Web_ selector beneath the _Services_ tab. These also include proxies, load balancers (LB), and streaming services.
|
||||
|
||||
| Service | Collectors | Context #1 | Context #2 | Context #3 |
|
||||
|--- |--- |--- |--- |--- |
|
||||
| Apache | `python.d.plugin:apache`, `go.d.plugin:apache` | `apache.requests` | `apache.connections` | `apache.net ` |
|
||||
| nginx | `python.d.plugin:nginx`, `go.d.plugin:nginx` | `nginx.requests` | `nginx.connections` | |
|
||||
| nginx+ | `python.d.plugin:nginx_plus` | `nginx_plus.requests_total` | `nginx_plus.connections_statistics` | |
|
||||
| lighthttpd | `python.d.plugin:lighttpd`, `go.d.plugin:lighttpd` | `lighttpd.requests` | `lighttpd.net` | |
|
||||
| lighthttpd2 | `go.d.plugin:lighttpd2` | `lighttpd2.requests` | `lighttpd2.traffic` | |
|
||||
| LiteSpeed | `python.d.plugin:litespeed` | `litespeed.requests` | `litespeed.requests_processing` | |
|
||||
| Tomcat | `python.d.plugin:tomcat` | `tomcat.accesses` | `tomcat.processing_time` | `tomcat.bandwidth` |
|
||||
| PHP FPM | `python.d.plugin:phpfm` | `phpfpm.performance` | `phpfpm.requests` | `phpfpm.connections` |
|
||||
| HAproxy | `python.d.plugin:haproxy` | `haproxy_f.scur` | `haproxy_f.bin` | `haproxy_f.bout` |
|
||||
| Squid | `python.d.plugin:squid` | `squid.clients_requests` | `squid.clients_net` | |
|
||||
| Traefik | `python.d.plugin:traefik` | `traefik.response_codes` | | |
|
||||
| Varnish | `python.d.plugin:varnish` | `varnish.session_connection` | `varnish.client_requests` | |
|
||||
| IPVS | `proc.plugin:/proc/net/ip_vs_stats` | `ipvs.sockets` | `ipvs.packets` | |
|
||||
| Web Log | `python.d.plugin:web_log`, `go.d.plugin:web_log` | `web_log.response_codes` | `web_log.bandwidth` | |
|
||||
| IPFS | `python.d.plugin:ipfs` | `ipfs.bandwidth` | `ipfs.peers` | |
|
||||
| IceCast Media Streaming | `python.d.plugin:icecast` | `icecast.listeners` | | |
|
||||
| RetroShare | `python.d.plugin:retroshare` | `retroshare.bandwidth` | `retroshare.peers` | |
|
||||
| HTTP Check | `python.d.plugin:httpcheck`, `go.d.plugin:httpcheck` | `httpcheck.responsetime` | `httpcheck.status` | |
|
||||
| x509 Check | `go.d.plugin:x509check` | `x509check.time_until_expiration` | | |
|
||||
|
||||
### Messaging
|
||||
|
||||
These services will appear under the _Messaging_ selector beneath the _Services_ tab.
|
||||
|
||||
| Service | Collectors | Context #1 | Context #2 | Context #3 |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| RabbitMQ | `python.d.plugin:rabbitmq`, `go.d.plugin:rabbitmq` | `rabbitmq.queued_messages` | `rabbitmq.erlang_run_queue` |
|
||||
| Beanstalkd | `python.d.plugin:beanstalk` | `beanstalk.total_jobs_rate` | `beanstalk.connections_rate` | `beanstalk.current_tubes` |
|
||||
|
||||
[](<>)
|
||||
|
|
@ -1,175 +0,0 @@
|
|||
<!--
|
||||
---
|
||||
title: "Registration and signing in"
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/netdata-cloud/signing-in.md
|
||||
---
|
||||
-->
|
||||
|
||||
# Registration and signing in
|
||||
|
||||
To use the features of [Netdata Cloud](/docs/netdata-cloud/README.md), you must first register an account with Netdata
|
||||
Cloud and associate your first Netdata node with the Netdata Cloud [registry](/registry/README.md). **Netdata Cloud is
|
||||
entirely free for all Netdata users**, and does not store any metrics created by your machines. You keep your
|
||||
data—Netdata Cloud just connects it all together.
|
||||
|
||||
> By [signing in](/docs/netdata-cloud/signing-in.md) to Netdata Cloud, you opt-in to let Netdata Cloud receive and store
|
||||
> the information described [here](/registry/README.md#what-data-does-the-registry-store). We never store the metrics
|
||||
> collected by Netdata agents, just machine GUIDs, person GUID, URLs, and account information.
|
||||
|
||||
## Registering a Netdata Cloud account
|
||||
|
||||
There is only one prerequisite to using Netdata Cloud: A working Netdata agent. If you don't have a running Netdata
|
||||
agent yet, check out the [installation guides](/packaging/installer/README.md) for more information.
|
||||
|
||||
To begin, visit the web dashboard of your Netdata agent by navigating your browser of choice to `http://SERVER-IP:19999`. You’ll see a dashboard much like this:
|
||||
|
||||
|
||||
|
||||
From here, you need to register for a Netdata Cloud account. Click on the **Sign in** button on the top-right corner of the dashboard's view.
|
||||
|
||||
|
||||
|
||||
??? note "Alternative registration routes"
|
||||
While we recommend the **Sign in** button, the Netdata dashboard has one other direct route registering for or signing in to a Netdata Cloud account.
|
||||
|
||||
|
||||
The text **Please sign in to netdata.cloud to view your nodes!** contains a link to access Netdata Cloud.
|
||||
|
||||
|
||||
|
||||
Two other routes exist, but they are more directly related to accessing the Nodes View. They will, however, require either registration or sign in and thus are valid routes to access Netdata Cloud.
|
||||
|
||||
One route can be found in the **Nodes Beta** button the left side of the navigation menu:
|
||||
|
||||
|
||||
|
||||
A second route can be found in the Nodes List—the drop-down menu in the top-left corner of the Netdata dashboard:
|
||||
|
||||
|
||||
|
||||
|
||||
??? note "Registration route when using a private registry"
|
||||
If you're using a private registry, clicking the **Sign in** button will display a modal window warning you about the process of migrating away from your private registry and to Netdata Cloud's registry.
|
||||
|
||||
|
||||
|
||||
|
||||
If you agree to use Netdata Cloud over your private registry, and opt-in to let Netdata Cloud receive and store the information described [here](/registry/README.md#what-data-does-the-registry-store), you should click the **Sign in** button again. If not, click the **Cancel** button to continue using your private registry.
|
||||
|
||||
|
||||
### Choosing your registration or sign in method
|
||||
|
||||
After clicking the **Sign in** button, you'll be directed to the Netdata Cloud registration/sign in page. Choose to authorize with your Google account, GitHub account, or email.
|
||||
|
||||
!!! attention
|
||||
Be consistent with the sign in method you use, whether GitHub, Google, or email. If you sign in via different methods, the system will create multiple Netdata Cloud accounts, one for each sign-in method used. We plan to offer multiple authentication methods for the same account in the future.
|
||||
|
||||
|
||||
|
||||
### Registration via Google
|
||||
|
||||
Click the **Authorize with Google** button to begin registration. You will be redirected to a Google authentication form where you confirm you will "share your name, email address, language preference, and profile picture with netdata.cloud."
|
||||
|
||||
|
||||
|
||||
Click on the account you would like to connect to Netdata Cloud to continue and then skip down to [Visiting Netdata Cloud for the first time](#visiting-the-nodes-view-for-the-first-time) for further instructions.
|
||||
|
||||
### Registration via GitHub
|
||||
|
||||
Click the **Authorize with GitHub** button to begin registration. You will be redirected to a GitHub authentication form where you confirm to share your email address with Netdata Cloud to create your account.
|
||||
|
||||
|
||||
|
||||
Click the **Authorize Netdata** button to continue and then skip down to [Visiting Netdata Cloud for the first time](#visiting-the-nodes-view-for-the-first-time) for further instructions.
|
||||
|
||||
### Registration via email
|
||||
|
||||
Enter your preferred email into the field and click the **Authorize** button.
|
||||
|
||||
Open your email account and check for the verification email—it should arrive in less than a minute. If it doesn't show up, check your spam folder or click the **Resend email** button in the Netdata Cloud interface.
|
||||
|
||||
When the email arrives, open it and click on the green **Sign in** button and then skip down to [Visiting Netdata Cloud for the first time](#visiting-the-nodes-view-for-the-first-time) for further instructions.
|
||||
|
||||
|
||||
|
||||
## Visiting the Nodes View for the first time
|
||||
|
||||
Regardless of which sign in method you used, you'll now be redirected back to your Netdata agent's dashboard. This node has now been associated with your Netdata Cloud account. Netdata Cloud uses a list of nodes associated with your account to populate the Nodes List dropdown in the dashboard and the Nodes View feature of Netdata Cloud.
|
||||
|
||||
**For more information on how to use the Nodes View, visit the [Nodes View guide](nodes-view.md).**
|
||||
|
||||
## Signing in to your Netdata Cloud account
|
||||
|
||||
The process of signing in to an existing Netdata Cloud account the same as [registering for a new account](#registering-a-netdata-cloud-account). The recommended method is to use the **Sign in** button at the top-right corner of a Netdata nodes's dashboard. Choose the method you used to register for your Netdata Cloud account and complete the process.
|
||||
|
||||
|
||||
|
||||
## Adding additional nodes to your Netdata Cloud account
|
||||
|
||||
There is currently only one way to associate additional Netdata nodes with your Netdata Cloud account: You must visit the web dashboard for each node and click the **Sign in** button and complete the [sign in process](#signing-in-to-your-netdata-cloud-account).
|
||||
|
||||
!!! note ""
|
||||
We are aware that the process of registering each node individually is cumbersome for those who want to implement Netdata Cloud's features across a large infrastructure.
|
||||
|
||||
```
|
||||
Please view [this comment on issue #6318](https://github.com/netdata/netdata/issues/6318#issuecomment-504106329) for how we plan on improving the process for adding additional nodes to your Netdata Cloud account.
|
||||
```
|
||||
|
||||
## Private registries and Netdata Cloud
|
||||
|
||||
If you use a [private registry](/registry/README.md#run-your-own-registry), and sign in to Netdata Cloud, you'll be using the Netdata Cloud registry in addition to your private registry.
|
||||
|
||||
Clicking the **Sign in** button on the Netdata dashboard will display a modal window warning you about the synchronization of your private registry's entries to the Netdata Cloud's registry.
|
||||
|
||||
|
||||
|
||||
If your company's data policies don't allow storing information about your nodes on the Netdata Cloud registry, you
|
||||
should click the **Cancel** button and continue using your private registry. You'll be able to access the Nodes List in
|
||||
the top-left corner of a Netdata dashboard, but you won't be able to use the [Nodes View](nodes-view.md) feature within
|
||||
Netdata Cloud, or any of the [additional
|
||||
features](https://blog.netdata.cloud/posts/netdata-cloud-announcement/#what-features-will-netdata-cloud-offer) on our
|
||||
roadmap. You can also sign up for the waiting list for the [hosted and/or on-premises versions of Netdata
|
||||
Cloud](/docs/netdata-cloud/README.md#running-netdata-cloud-on-premises-or-as-a-hosted-instance) that we're working on.
|
||||
|
||||
If you agree to use Netdata Cloud over your private registry, and opt-in to let Netdata Cloud receive and store the information described [here](/registry/README.md#what-data-does-the-registry-store), you should click the **Sign in** button again to continue the registration/sign in process.
|
||||
|
||||
### Returning to your private registry
|
||||
|
||||
If you register for or sign in to Netdata Cloud from a node previously associated with a private registry, you can easily return to your private registry by signing out.
|
||||
|
||||
You can sign out in two ways:
|
||||
|
||||
1. **From a node's dashboard**: In the top-right corner you will find a dropdown menu with your email address. Click that and then click the **Sign Out** button.
|
||||
2. **From Netdata Cloud**: Click on your profile picture in the top-right corner and then click on the **Sign Out** button.
|
||||
|
||||
Signing out from Netdata Cloud and returning to your private registry *does not remove* the [information stored](/registry/README.md#what-data-does-the-registry-store) about your nodes or account details.
|
||||
|
||||
But, upon signout, your Nodes List on all dashboards will once more be populated by your private registry and not Netdata Cloud.
|
||||
|
||||
<!-- ## The 'Synchronize with Netdata Cloud' button
|
||||
|
||||
Once signed in to Netdata Cloud, the Nodes List dropdown will now show a button labeled `Synchronize with netdata.cloud`.
|
||||
|
||||
The `Synchronize with Netdata Cloud` button is a migration (or import) tool for Netdata Cloud. If either the public or your private registry contains a list of nodes associated with your `person_guid`, it will import them into Netdata Cloud and associate them with the `accounts` information in the Netdata Cloud registry.
|
||||
|
||||
When you click the `Synchronize with netdata.cloud` button, you will receive one of two popup messages based on whether you were using the public registry (at `registry.my-netdata.io`) or a private registry.
|
||||
|
||||
**Public registry**:
|
||||
|
||||
|
||||
|
||||
**Private registry**:
|
||||
|
||||
|
||||
|
||||
If you do not want to synchronize your registry of choice with Netdata Cloud, click `Cancel`.
|
||||
|
||||
If you do, click `Synchronize`. This will push GUIDs, hostnames, and URLs to Netdata Cloud's registry.
|
||||
|
||||
Now, when you visit the Nodes View, you will be able to see all the nodes that were once associated with the public/private registry you were using previously. -->
|
||||
|
||||
## What's next?
|
||||
|
||||
Learn how to use the [Nodes View](nodes-view.md) to monitor many nodes concurrently.
|
||||
|
||||
[](<>)
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
---
|
||||
title: "Step 2. Get to know Netdata's dashboard"
|
||||
date: 2020-03-11
|
||||
date: 2020-05-04
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/step-by-step/step-02.md
|
||||
---
|
||||
-->
|
||||
|
|
@ -28,30 +28,19 @@ In this step of the Netdata guide, you'll learn how to:
|
|||
|
||||
Let's get started!
|
||||
|
||||
<details markdown="1"><summary>Like shortcuts? Watch our six-minute quickstart video for Netdata's dashboard.</summary>
|
||||
<iframe width="720" height="405" src="https://www.youtube.com/embed/Ob6-Wkb6ZBA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
<p>Once you've finished, <a href="#whats-next">skip ahead</a> or scroll down for the text-based dashboard quickstart.</p>
|
||||
</details>
|
||||
|
||||
## Visit and explore the dashboard
|
||||
|
||||
Netdata's dashboard is where you interact with your system's metrics. Time to open it up and start exploring. Open up
|
||||
your browser of choice.
|
||||
|
||||
If you installed Netdata on the same system you're using to open your browser, navigate to `http://localhost:19999/`.
|
||||
|
||||
If you installed Netdata on a remote system, navigate to `http://HOST:19999/` after replacing `HOST` with the IP address
|
||||
of that system. To connect to a virtual private server (VPS), for example, you might navigate to
|
||||
`http://203.0.113.0:19999`. We'll learn more on monitoring remote systems and [multiple systems](step-03.md)
|
||||
later on.
|
||||
|
||||
> From here on out in this tutorial, we'll refer to the address you use to view your dashboard as `HOST`. Be sure to
|
||||
> replace it with either `localhost` or the IP address as needed.
|
||||
|
||||
Hit `Enter`. Welcome to Netdata!
|
||||
Open up your web browser of choice and navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname
|
||||
of your Agent. If you're unsure, try `http://localhost:19999` first. Hit **Enter**. Welcome to Netdata!
|
||||
|
||||
|
||||
dashboard](https://user-images.githubusercontent.com/1153921/80825153-abaec600-8b94-11ea-8b17-1b770a2abaa9.gif)
|
||||
|
||||
> From here on out in this tutorial, we'll refer to the address you use to view your dashboard as `NODE`. Be sure to
|
||||
> replace it with either `localhost`, the IP address, or the hostname of your system.
|
||||
|
||||
## Explore available charts using menus
|
||||
|
||||
|
|
@ -59,7 +48,7 @@ dashboard](https://user-images.githubusercontent.com/1153921/63463901-fcb9c800-c
|
|||
charts you're interested in.
|
||||
|
||||
|
||||
submenus](https://user-images.githubusercontent.com/1153921/80832425-7c528600-8ba1-11ea-8140-d0a17a62009b.gif)
|
||||
|
||||
Netdata shows all its charts on a single page, so you can also scroll up and down using the mouse wheel, your
|
||||
touchscreen/touchpad, or the scrollbar.
|
||||
|
|
@ -69,7 +58,7 @@ what it's collecting. If you run Netdata on many different systems using differe
|
|||
menus and submenus may look a little different for each one.
|
||||
|
||||
To learn more about menus, see our documentation about [navigating the standard
|
||||
dashboard](/web/gui/README.md#menus).
|
||||
dashboard](/web/gui/README.md#metrics-menus).
|
||||
|
||||
> ❗ By default, Netdata only creates and displays charts if the metrics are _not zero_. So, you may be missing some
|
||||
> charts, menus, and submenus if those charts have zero metrics. You can change this by changing the **Which dimensions
|
||||
|
|
@ -128,11 +117,10 @@ We built Netdata to be a big sandbox for learning more about your systems and ap
|
|||
Netdata's charts are fully interactive. You can pan through historical metrics, zoom in and out, select specific
|
||||
timeframes for further analysis, resize charts, and more.
|
||||
|
||||
Best of all, Whenever you use a chart in this way, Netdata synchronizes all the other charts to match it. This even
|
||||
applies across different Netdata agents if you connect them using the [**My nodes** menu](/registry/README.md)!
|
||||
Best of all, Whenever you use a chart in this way, Netdata synchronizes all the other charts to match it.
|
||||
|
||||
|
||||
|
||||
|
||||
### Pan, zoom, highlight, and reset charts
|
||||
|
||||
|
|
@ -149,9 +137,6 @@ You can change how charts show their metrics in a few different ways, each of wh
|
|||
These interactions can also be triggered using the icons on the bottom-right corner of every chart. They are,
|
||||
respectively, `Pan Left`, `Reset`, `Pan Right`, `Zoom In`, and `Zoom Out`.
|
||||
|
||||
|
||||
|
||||
### Show and hide dimensions
|
||||
|
||||
Each dimension can be hidden by clicking on it. Hiding dimensions simplifies the chart and can help you better discover
|
||||
|
|
@ -163,40 +148,40 @@ Additionally, resize charts by clicking-and-dragging the icon on the bottom-righ
|
|||
chart to its original height, double-click the same icon.
|
||||
|
||||
|
||||
height](https://user-images.githubusercontent.com/1153921/80842459-7d41e280-8bb6-11ea-9488-1bc29f94d7f2.gif)
|
||||
|
||||
To learn more about other options and chart interactivity, read our [dashboard documentation](/web/README.md).
|
||||
|
||||
## See raised alarms and the alarm log
|
||||
|
||||
Aside from performance troubleshooting, Netdata is designed to help you monitor the health of your systems and
|
||||
applications. That's why every Netdata installation comes with dozens of pre-configured alarms that trigger alerts when
|
||||
your system starts acting strangely.
|
||||
Aside from performance troubleshooting, the Agent helps you monitor the health of your systems and applications. That's
|
||||
why every Netdata installation comes with dozens of pre-configured alarms that trigger alerts when your system starts
|
||||
acting strangely.
|
||||
|
||||
Find the **Alarms** button in the top navigation bring up a modal that shows currently raised alarms, all running
|
||||
alarms, and the alarms log.
|
||||
|
||||
Here is an example of raised `disk_space._` and `disk_space._home` alarms, followed by the full list and alarm log:
|
||||
Here is an example of a raised `system.cpu` alarm, followed by the full list and alarm log:
|
||||
|
||||
|
||||
log](https://user-images.githubusercontent.com/1153921/80842482-8c289500-8bb6-11ea-9791-600cfdbe82ce.gif)
|
||||
|
||||
Let's look at one of those raised alarms a little more in-depth. Here is a static screenshot:
|
||||
And a static screenshot of the raised CPU alarm:
|
||||
|
||||
|
||||
|
||||
|
||||
The alarm itself is named **disk - /**, and its context is `disk_space._`. Beneath that is an auto-updating badge that
|
||||
shows the latest metric: 28.4% disk space usage.
|
||||
The alarm itself is named *system - cpu**, and its context is `system.cpu`. Beneath that is an auto-updating badge that
|
||||
shows the latest value the chart that triggered the alarm.
|
||||
|
||||
With the three icons beneath that and the **role** designation, you can **1)** scroll to the chart associated with this
|
||||
raised alarm, **2)** copy a link to the badge to your clipboard, and **3)** copy the code to embed the badge onto
|
||||
another web page using an `<embed>` element.
|
||||
With the three icons beneath that and the **role** designation, you can:
|
||||
|
||||
The table on the right-hand side displays information about the alarm's configuration.
|
||||
1. Scroll to the chart associated with this raised alarm.
|
||||
2. Copy a link to the badge to your clipboard.
|
||||
3. Copy the code to embed the badge onto another web page using an `<embed>` element.
|
||||
|
||||
In this example, Netdata triggers a warning alarm when any disk on the system is more than 20% full. Netdata triggers a
|
||||
critical alarm when the disk is more than 30% full.
|
||||
The table on the right-hand side displays information about the alarm's configuration. In above example, Netdata
|
||||
triggers a warning alarm when CPU usage is between 75 and 85%, and a critical alarm when above 85%. It's a _little_ more
|
||||
complicated than that, but we'll get into more complex health entity configurations in a later step.
|
||||
|
||||
The `calculation` field is the equation used to calculate those percentages, and the `check every` field specifies how
|
||||
often Netdata should be calculating these metrics to see if the alarm should remain triggered.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
<!--
|
||||
---
|
||||
title: "Step 3. Monitor more than one system with Netdata"
|
||||
date: 2020-05-01
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/step-by-step/step-03.md
|
||||
---
|
||||
-->
|
||||
|
|
@ -15,158 +16,76 @@ You might be thinking, "So, now I have to remember all these IP addresses, and t
|
|||
manually, to move from one system to another? Maybe I should just make a bunch of bookmarks. What's a few more tabs
|
||||
on top of the hundred I have already?"
|
||||
|
||||
We get it. That's why we built [Netdata Cloud](/docs/netdata-cloud/README.md), which connects many distributed agents
|
||||
together for a seamless experience when monitoring multiple systems.
|
||||
We get it. That's why we built [Netdata Cloud](https://learn.netdata.cloud/docs/cloud/), which connects many distributed
|
||||
agents for a seamless experience when monitoring an entire infrastructure of Netdata-monitored nodes.
|
||||
|
||||
All without remembering IPs or making a bunch of bookmarks.
|
||||
|
||||
> If you're interested in streaming the metrics from one Netdata agent to another, that's unfortunately not part of this
|
||||
> tutorial. You'll want to reference our [streaming documentation](/streaming/README.md) when you're finished with
|
||||
> these steps.
|
||||
|
||||
Even if you don't have multiple systems right now, keep reading. The instructions to follow will show you how to test
|
||||
out these features with Netdata demo servers. That way, you'll be able to experience one of Netdata's defining features
|
||||
right away.
|
||||
|
||||
|
||||
## What you'll learn in this step
|
||||
|
||||
In this step of the Netdata guid, we'll talk about the following:
|
||||
In this step of the Netdata guide, we'll talk about the following:
|
||||
|
||||
- [Why you should use Netdata Cloud](#why-use-netdata-cloud)
|
||||
- [Add nodes to your Netdata Cloud account](#add-nodes-to-your-netdata-cloud-account)
|
||||
- [Navigate between your nodes via the **My nodes** menu](#navigate-between-your-nodes-via-the-my-nodes-menu)
|
||||
- [Try out the Nodes View](#try-out-the-nodes-view)
|
||||
- [Get started with Netdata Cloud](#get-started-with-netdata-cloud)
|
||||
- [Navigate between dashboards with Visited Nodes](#navigate-between-dashboards-with-visited-nodes)
|
||||
|
||||
## Why use Netdata Cloud?
|
||||
|
||||
We built Netdata Cloud to give users a way to bridge the gap between many distributed agents running concurrently, all
|
||||
without creating a centralized database for all your systems' metrics.
|
||||
Our [Cloud documentation](https://learn.netdata.cloud/docs/cloud/) does a good job (we think!) of explaining why Cloud
|
||||
gives you a ton of value at no cost:
|
||||
|
||||
Netdata Cloud gives you a better way to observe and take action on slowdowns, anomalies, or outages in your systems and
|
||||
applications. It connects all your Netdata agents through your _web browser_, allowing you to move between different
|
||||
nodes quickly and use the Nodes View to see a handful or hundreds of Netdata-monitored nodes on a single screen.
|
||||
> Netdata Cloud gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can run all your
|
||||
> distributed Agents in headless mode _and_ access the real-time metrics and insightful charts from their dashboards.
|
||||
> View key metrics and active alarms at-a-glance, and then seamlessly dive into any of your distributed dashboards
|
||||
> without leaving Cloud's centralized interface.
|
||||
|
||||
If you're keeping tabs on multiple systems with Netdata, Netdata Cloud gives you all the benefits of a centralized
|
||||
monitoring solution while distributing the workload to each agent.
|
||||
You can as made nodes and team members as you need, and as our free and open source Agent gets better with more
|
||||
features, new collectors for more applications, and improved UI, so will Cloud.
|
||||
|
||||
That makes Netdata Cloud both comprehensive and lightweight. The best of both worlds!
|
||||
## Get started with Netdata Cloud
|
||||
|
||||
And, better yet, Netdata Cloud doesn't store any of your system's metrics. It stores _metadata_ about the system's IP,
|
||||
hostname, and a randomly-created GUID, and nothing else. Metrics are streamed from your systems directly to your _web
|
||||
browser_.
|
||||
Signing in, onboarding, and claiming 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.
|
||||
|
||||
Essentially, your web browser hosts a SaaS application with all of Netdata Cloud's features embedded right into the
|
||||
dashboard itself.
|
||||
Or, if you're feeling confident, dive right in.
|
||||
|
||||
## Add nodes to your Netdata Cloud account
|
||||
<p><a href="https://app.netdata.cloud" className="button button--lg">Sign in to Cloud</a></p>
|
||||
|
||||
The best way to add nodes to your Netdata Cloud account is to click on the **Sign in** button on the top-right corner of
|
||||
your Netdata dashboard.
|
||||
When you finish that guide, circle back to this step in the tutorial to learn how to use the Visited Nodes feature on
|
||||
top of Cloud's centralized web interface.
|
||||
|
||||
That button will open a new tab in for Netdata Cloud, and will prompt you to log-in using email or authentication via
|
||||
Google or GitHub.
|
||||
## Navigate between dashboards with Visited Nodes
|
||||
|
||||
If you chose email, Netdata Cloud will send you a "magic link" via email. Once you click on the link, that node will be
|
||||
connected to your Netdata Cloud account and you'll be redirected back to your dashboard. If you chose Google or GitHub,
|
||||
you'll be redirected back to your dashboard as soon as authentication is finished.
|
||||
To add nodes to your visited nodes, you first need to navigate to that node's dashboard, then click the **Sign in**
|
||||
button at the top of the dashboard. On the screen that appears, which states your node is requesting access to your
|
||||
Netdata Cloud account, sign in with your preferred method.
|
||||
|
||||
Here's what authentication via Google looks like:
|
||||
Cloud redirects you back to your node's dashboard, which is now connected to your Netdata Cloud account. You can now see the menu populated by a single visited node.
|
||||
|
||||
|
||||
|
||||
|
||||
Depending on your authentication method, your email address or name will appear in the top right of your dashboard
|
||||
instead of the **Sign in** button.
|
||||
If you previously went through the Cloud onboarding process to create a Space and War Room, you will also see these
|
||||
alongside your visited nodes. You can click on your Space or any of your War Rooms to navigate to Netdata Cloud and
|
||||
continue monitoring your infrastructure from there.
|
||||
|
||||
At this point, you've successfully added a single Netdata agent to your Netdata Cloud account. _What about the rest?_
|
||||
|
||||
|
||||
Well, all you have to do is visit another node and repeat the sign-in process.
|
||||
To add other visited nodes, navigate to their dashboard and sign in to Cloud by clicking on the **Sign in** button. This
|
||||
process connects that node to your Cloud account and further populates the menu.
|
||||
|
||||
Let's use a demo system as an example.
|
||||
Once you've added more than one node, you can use the menu to switch between various dashboards without remembering IP
|
||||
addresses or hostnames or saving bookmarks for every node you want to monitor.
|
||||
|
||||
Visit the [Netdata website](https://www.netdata.cloud/#live-demo) and click on any of the gauge charts displayed
|
||||
underneath the **Live Demo** header.
|
||||
|
||||
Once the dashboard loads, repeat the Netdata Cloud sign-in process. The demo server is now associated with your Netdata
|
||||
Cloud account, and will appear in your **My nodes** menu.
|
||||
|
||||
Here's how the process looks in action:
|
||||
|
||||
|
||||
|
||||
## Navigate between your nodes via the My nodes menu
|
||||
|
||||
Once you have multiple nodes added to Netdata Cloud, they will populate your **My nodes** menu. You can use this menu to
|
||||
navigate between your systems quickly.
|
||||
|
||||
|
||||
|
||||
Whenever you pan, zoom, highlight, select, or pause a chart, Netdata will synchronize those settings with any other
|
||||
agent you visit via the My nodes menu. Even your scroll position is synchronized, so you'll see the same charts and
|
||||
respective data for easy comparisons or root cause analysis.
|
||||
|
||||
You can now seamlessly track performance anomalies across your entire infrastructure!
|
||||
|
||||
## Try out the Nodes View
|
||||
|
||||
Next, let's try out the Nodes View.
|
||||
|
||||
Nodes View is a feature built in to Netdata Cloud that offers a different interface for viewing the health status of
|
||||
multiple nodes.
|
||||
|
||||
> Learn more about all the features within Nodes View and what charts/metrics are represented there in our
|
||||
> [documentation](/docs/netdata-cloud/nodes-view.md).
|
||||
|
||||
You can visit Nodes View by navigating to `https://netdata.cloud/console` in your browser. Or, you can click on the
|
||||
**Nodes View** button in any Netdata dashboard. If you're not logged in to Netdata Cloud yet, you'll be asked to log in
|
||||
first.
|
||||
|
||||
|
||||
|
||||
The Nodes View shows an aggregated list of the nodes you connected to Netdata Cloud, and shows at-a-glance health status
|
||||
for each.
|
||||
|
||||
Click on any of the boxes representing your nodes to see real-time, per-second charts of essential metrics in the **Node
|
||||
overview** sidebar.
|
||||
|
||||
|
||||
|
||||
You can also view raised alarms and see real-time metrics from a [select number of
|
||||
services/applications](/docs/netdata-cloud/nodes-view.md#services-available-in-the-nodes-view) using the various tabs
|
||||
available in the node overview sidebar.
|
||||
|
||||
If you add a large number of nodes to the Nodes View, you may want to look into the different view and sorting options.
|
||||
You can choose between **full**, **compact**, and **detailed** view modes.
|
||||
|
||||
|
||||
|
||||
You can also sort between grouping nodes by hostname, recently viewed, or most frequestly visited. Or, group them by
|
||||
alarm status, their services, or whether they're online or unreachable.
|
||||
|
||||
|
||||
|
||||
Play around until you find the right settings for you and your infrastructure.
|
||||
|
||||
### Remove a node from Nodes View
|
||||
|
||||
If you want to clean up your Nodes View a bit, you can remove them from your Netdata Cloud account.
|
||||
|
||||
Click on the node in question, and then scroll to the bottom of the Node overiew sidebar. You'll see a URL under the
|
||||
**Node URLs** heading. Hover over the URL and click on the garbage bin icon. Click **Confirm** on the modal window.
|
||||
Then, click the **Forget** button that appears in the sidebar, and hit **Confirm** once again.
|
||||
|
||||
|
||||
|
||||
|
||||
## What's next?
|
||||
|
||||
Now that you know how to add multiple nodes to your Netdata Cloud agent and navigate between them, 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.
|
||||
Now that you have a Netdata Cloud account with a claimed 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.
|
||||
|
||||
[Next: The basics of configuring Netdata →](step-04.md)
|
||||
|
|
|
|||
|
|
@ -108,10 +108,10 @@ Here's the process in GIF form!
|
|||
|
||||
|
||||
Now, let's make a slightly more substantial edit to `netdata.conf`—change the agent's name.
|
||||
Now, let's make a slightly more substantial edit to `netdata.conf`: change the Agent's name.
|
||||
|
||||
If you edit the value of the `hostname` option, you can change the name of your Netdata agent on the dashboard and a
|
||||
handful of other places, like the **My nodes** menu.
|
||||
If you edit the value of the `hostname` option, you can change the name of your Netdata Agent on the dashboard and a
|
||||
handful of other places, like the Visited nodes menu _and_ Netdata Cloud.
|
||||
|
||||
Use `edit-config` to change the `hostname` option to a name like `hello-world`. Be sure to uncomment it!
|
||||
|
||||
|
|
@ -123,7 +123,7 @@ Use `edit-config` to change the `hostname` option to a name like `hello-world`.
|
|||
Once you're done, restart Netdata and refresh the dashboard. Say hello to your renamed agent!
|
||||
|
||||
|
||||
netdata.conf](https://user-images.githubusercontent.com/1153921/80994808-1c065300-8df2-11ea-81af-d28dc3ba27c8.gif)
|
||||
|
||||
Netdata has dozens upon dozens of options you can change. To see them all, read our [daemon
|
||||
configuration](/daemon/config/README.md), or hop into our popular tutorial on [increasing long-term metrics
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
<!--
|
||||
---
|
||||
title: "Step 7. Netdata's dashboard in depth"
|
||||
date: 2020-05-04
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/step-by-step/step-07.md
|
||||
---
|
||||
-->
|
||||
|
|
@ -31,14 +32,9 @@ operation of your Netdata server/daemon. They take effect immediately and are pe
|
|||
You can see the **Performance**, **Synchronization**, **Visual**, and **Locale** tabs on the dashboard settings modal.
|
||||
|
||||
|
||||
modal](https://user-images.githubusercontent.com/1153921/80841197-c93f5800-8bb3-11ea-907d-85bfe23565e1.gif)
|
||||
|
||||
To change any setting, click on the toggle button.
|
||||
|
||||
|
||||
|
||||
We recommend you spend some time reading the descriptions for each setting to understand them before making changes.
|
||||
To change any setting, click on the toggle button. We recommend you spend some time reading the descriptions for each setting to understand them before making changes.
|
||||
|
||||
Pay particular attention to the following settings, as they have dramatic impacts on the performance and appearance of
|
||||
your Netdata dashboard:
|
||||
|
|
@ -55,8 +51,7 @@ Some settings are applied immediately, and others are only reflected after you r
|
|||
|
||||
You can always check if there is an update available from the **Update** area of your Netdata dashboard.
|
||||
|
||||
|
||||
|
||||
|
||||
If an update is available, you'll see a modal similar to the one above.
|
||||
|
||||
|
|
@ -84,7 +79,7 @@ snapshot, and send it to a colleague for further analysis.
|
|||
To export a snapshot, click on the **export** icon.
|
||||
|
||||
|
||||
modal](https://user-images.githubusercontent.com/1153921/80993197-82d63d00-8def-11ea-88fa-98827814e930.gif)
|
||||
|
||||
Edit the snapshot file name and select your desired compression method. Click on **Export**.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
---
|
||||
title: "What is Netdata?"
|
||||
date: 2020-04-07
|
||||
date: 2020-05-01
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/what-is-netdata.md
|
||||
---
|
||||
-->
|
||||
|
|
@ -59,7 +59,7 @@ Netdata!](https://img.shields.io/twitter/url/http/shields.io.svg?style=social&la
|
|||
6. [Infographic](#infographic) - Everything about Netdata in a single graphic
|
||||
7. [Features](#features) - How you'll use Netdata on your systems
|
||||
8. [Visualization](#visualization) - Learn about visual anomaly detection
|
||||
9. [What Netdata monitors](#what-netdata-monitors) - See which apps/services Netdata auto-detects
|
||||
9. [What Netdata monitors](#what-netdata-monitors) - See which apps/services Netdata auto-detects
|
||||
10. [Documentation](#documentation) - Read the documentation
|
||||
11. [Community](#community) - Discuss Netdata with others and get support
|
||||
12. [License](#license) - Check Netdata's licencing
|
||||
|
|
@ -71,7 +71,7 @@ Netdata!](https://img.shields.io/twitter/url/http/shields.io.svg?style=social&la
|
|||
The following animated GIF shows the top part of a typical Netdata dashboard.
|
||||
|
||||
|
||||
action](https://user-images.githubusercontent.com/1153921/80827388-b9fee100-8b98-11ea-8f60-0d7824667cd3.gif)
|
||||
|
||||
> A typical Netdata dashboard, in 1:1 timing. Charts can be panned by dragging them, zoomed in/out with `SHIFT` + `mouse
|
||||
> wheel`, an area can be selected for zoom-in with `SHIFT` + `mouse selection`. Netdata is highly interactive,
|
||||
|
|
@ -264,18 +264,17 @@ This is what you should expect from Netdata:
|
|||
|
||||
- **Sophisticated alerting** - Netdata comes with hundreds of alarms **out of the box**! It supports dynamic
|
||||
thresholds, hysteresis, alarm templates, multiple role-based notification methods, and more.
|
||||
- **Notifications**: [alerta.io](/health/notifications/alerta/README.md), [amazon
|
||||
sns](/health/notifications/awssns/README.md), [discordapp.com](/health/notifications/discord/README.md),
|
||||
[email](/health/notifications/email/README.md), [flock.com](/health/notifications/flock/README.md),
|
||||
[hangouts](/health/notifications/hangouts/README.md), [irc](/health/notifications/irc/README.md),
|
||||
[kavenegar.com](/health/notifications/kavenegar/README.md), [messagebird.com](/health/notifications/messagebird/),
|
||||
[pagerduty.com](/health/notifications/pagerduty/README.md), [prowl](/health/notifications/prowl/README.md),
|
||||
[pushbullet.com](/health/notifications/pushbullet/README.md),
|
||||
[pushover.net](/health/notifications/pushover/README.md), [rocket.chat](/health/notifications/rocketchat/README.md),
|
||||
[slack.com](/health/notifications/slack/README.md), [smstools3](/health/notifications/smstools3/README.md),
|
||||
[syslog](/health/notifications/syslog/README.md), [telegram.org](/health/notifications/telegram/README.md),
|
||||
[twilio.com](/health/notifications/twilio/README.md), [web](/health/notifications/web/README.md) and [custom
|
||||
notifications](/health/notifications/custom/README.md).
|
||||
- **Notifications**: [alerta.io](/health/notifications/alerta/), [amazon sns](/health/notifications/awssns/),
|
||||
[discordapp.com](/health/notifications/discord/), [email](/health/notifications/email/),
|
||||
[flock.com](/health/notifications/flock/), [hangouts](/health/notifications/hangouts/),
|
||||
[irc](/health/notifications/irc/), [kavenegar.com](/health/notifications/kavenegar/),
|
||||
[messagebird.com](/health/notifications/messagebird/), [pagerduty.com](/health/notifications/pagerduty/),
|
||||
[prowl](/health/notifications/prowl/), [pushbullet.com](/health/notifications/pushbullet/),
|
||||
[pushover.net](/health/notifications/pushover/), [rocket.chat](/health/notifications/rocketchat/),
|
||||
[slack.com](/health/notifications/slack/), [smstools3](/health/notifications/smstools3/),
|
||||
[syslog](/health/notifications/syslog/), [telegram.org](/health/notifications/telegram/),
|
||||
[twilio.com](/health/notifications/twilio/), [web](/health/notifications/web/) and [custom
|
||||
notifications](/health/notifications/custom/).
|
||||
|
||||
### Integrations
|
||||
|
||||
|
|
@ -303,7 +302,8 @@ This is what you should expect from Netdata:
|
|||
To improve clarity on charts, Netdata dashboards present **positive** values for metrics representing `read`, `input`,
|
||||
`inbound`, `received` and **negative** values for metrics representing `write`, `output`, `outbound`, `sent`.
|
||||
|
||||
|
||||
|
||||
|
||||
_Netdata charts showing the bandwidth and packets of a network interface. `received` is positive and `sent` is
|
||||
negative._
|
||||
|
|
@ -312,7 +312,8 @@ negative._
|
|||
|
||||
Netdata charts automatically zoom vertically, to visualize the variation of each metric within the visible time-frame.
|
||||
|
||||
|
||||
|
||||
|
||||
_A zero-based `stacked` chart, automatically switches to an auto-scaled `area` chart when a single dimension is
|
||||
selected._
|
||||
|
|
@ -322,27 +323,23 @@ selected._
|
|||
Charts on Netdata dashboards are synchronized to each other. There is no master chart. Any chart can be panned or zoomed
|
||||
at any time, and all other charts will follow.
|
||||
|
||||
|
||||
|
||||
|
||||
_Charts are panned by dragging them with the mouse. Charts can be zoomed in/out with`SHIFT` + `mouse wheel` while the
|
||||
mouse pointer is over a chart._
|
||||
|
||||
> The visible time-frame (pan and zoom) is propagated from Netdata server to Netdata server when navigating via the
|
||||
> [My nodes menu](/registry/README.md).
|
||||
|
||||
### Highlighted time-frame
|
||||
|
||||
To improve visual anomaly detection across charts, the user can highlight a time-frame (by pressing `Alt` + `mouse
|
||||
selection`) on all charts.
|
||||
|
||||
|
||||
|
||||
|
||||
_A highlighted time-frame can be given by pressing `Alt` + `mouse selection` on any chart. Netdata will highlight the
|
||||
same range on all charts._
|
||||
|
||||
> Highlighted ranges are propagated from Netdata server to Netdata server, when navigating via the [My nodes
|
||||
> menu](/registry/README.md).
|
||||
|
||||
## What Netdata monitors
|
||||
|
||||
Netdata can collect metrics from 200+ popular services and applications, on top of dozens of system-related metrics
|
||||
|
|
@ -397,7 +394,7 @@ You can also find Netdata on:
|
|||
|
||||
## License
|
||||
|
||||
Netdata is GPLv3+.
|
||||
Netdata is [GPLv3+](/LICENSE).
|
||||
|
||||
Netdata re-distributes other open-source tools and libraries. Please check the [third party licenses](/REDISTRIBUTED.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -17,8 +17,7 @@ Before you update Netdata using one of the methods below, check to see if your N
|
|||
opening the update modal in the dashboard. Click the **Update** button in the top navigation to open it. The modal tells
|
||||
you whether your agent is up-to-date or not.
|
||||
|
||||
|
||||
|
||||
|
||||
If your agent can be updated, use one of the methods below. **The method you chose for updating Netdata depends on how
|
||||
you installed it.** Choose from the following list to see the appropriate update instructions for your system.
|
||||
|
|
|
|||
|
|
@ -50,8 +50,7 @@ forward or backward in time, or selecting a specific timeframe for more in-depth
|
|||
analysis.
|
||||
|
||||
Whenever you use a chart in this way, Netdata synchronizes all the other charts
|
||||
to match it. Chart synchronization even works between separate Netdata agents if you connect
|
||||
them using the [**My nodes** menu](/registry/README.md)!
|
||||
to match it.
|
||||
|
||||
You can change how charts show their metrics in a few different ways, each of
|
||||
which have a few methods:
|
||||
|
|
@ -66,14 +65,19 @@ which have a few methods:
|
|||
|
||||
Here's how chart synchronization looks while zooming and panning:
|
||||
|
||||
|
||||
|
||||
|
||||
You can also perform all these actions using the small
|
||||
rewind/play/fast-forward/zoom-in/zoom-out buttons that appear in the
|
||||
bottom-right corner of each chart.
|
||||
|
||||
Additionally, resize charts by clicking-and-dragging the icon on the bottom-right corner of any chart. To restore the
|
||||
chart to its original height, double-click the same icon.
|
||||
|
||||
|
||||
|
||||
## Charts, contexts, families
|
||||
|
||||
Before customizing the standard web dashboard, creating a custom dashboard,
|
||||
|
|
@ -191,7 +195,8 @@ To improve clarity on charts, Netdata dashboards present **positive** values for
|
|||
metrics representing `read`, `input`, `inbound`, `received` and **negative**
|
||||
values for metrics representing `write`, `output`, `outbound`, `sent`.
|
||||
|
||||
|
||||
|
||||
|
||||
_Netdata charts showing the bandwidth and packets of a network interface.
|
||||
`received` is positive and `sent` is negative._
|
||||
|
|
@ -201,7 +206,8 @@ _Netdata charts showing the bandwidth and packets of a network interface.
|
|||
Netdata charts automatically zoom vertically, to visualize the variation of each
|
||||
metric within the visible timeframe.
|
||||
|
||||
|
||||
|
||||
|
||||
_A zero-based `stacked` chart, automatically switches to an auto-scaled `area`
|
||||
chart when a single dimension is selected._
|
||||
|
|
|
|||
|
|
@ -1,25 +1,30 @@
|
|||
<!--
|
||||
---
|
||||
title: "The standard web dashboard"
|
||||
date: 2020-03-11
|
||||
date: 2020-05-04
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/web/gui/README.md
|
||||
---
|
||||
-->
|
||||
|
||||
# The standard web dashboard
|
||||
|
||||
The standard web dashboard is the heart of Netdata's performance troubleshooting
|
||||
toolkit. You've probably seen it before:
|
||||
The standard web dashboard is the heart of Netdata's performance troubleshooting toolkit. You've probably seen it
|
||||
before:
|
||||
|
||||
|
||||
|
||||
|
||||
Learn more about how dashboards work and how they're populated using the
|
||||
`dashboards.js` file in our [web dashboards overview](/web/README.md).
|
||||
|
||||
By default, Netdata starts a web server for its dashboard at port `19999`. Open
|
||||
up your web browser of choice and navigate to `http://SERVER-IP:19999`, or
|
||||
`http://localhost:19999` on `localhost`.
|
||||
By default, Netdata starts a web server for its dashboard at port `19999`. Open up your web browser of choice and
|
||||
navigate to `http://NODE:19999`, replacing `NODE` with the IP address or hostname of your Agent. If you're unsure, try
|
||||
`http://localhost:19999` first.
|
||||
|
||||
> In v1.21 of the Agent, we replaced the legacy dashboard with a refactored dashboard written in React. By using React,
|
||||
> we simplify our code and give our engineers better tools to add new features and fix bugs. The only UI change with
|
||||
> this dashboard is the top navigation and left-hand navigation for [Cloud integration](/docs/agent-cloud.md). The old
|
||||
> dashboard is still accessible at the `http://NODE:19999/old` subfolder.
|
||||
|
||||
Netdata uses an [internal, static-threaded web server](/web/server/README.md) to host the
|
||||
HTML, CSS, and JavaScript files that make up the standard dashboard. You don't
|
||||
|
|
@ -27,26 +32,16 @@ have to configure anything to access it, although you can adjust [your
|
|||
settings](/web/server/README.md#other-netdataconf-web-section-options) in the
|
||||
`netdata.conf` file, or run Netdata behind an Nginx proxy, and so on.
|
||||
|
||||
<details markdown="1"><summary>Want to see the dashboard and its features in action? Check out our video.</summary>
|
||||
<iframe width="720" height="405" src="https://www.youtube.com/embed/Ob6-Wkb6ZBA" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
</details>
|
||||
|
||||
## New React Dashboard
|
||||
|
||||
We've been working on refactoring the standard dashboard code to simplify the process of adding new features and fixing bugs.
|
||||
|
||||
The new dashboard is added to the codebase, but the old version is still here. If you want to use it, run `/usr/libexec/netdata/netdata-switch-dashboard.sh classic`. To switch back, do `netdata-switch-dashboard.sh react`. Currently, the refactored dashboard doesn't include any noticeable changes in UI.
|
||||
|
||||
## Navigating the standard dashboard
|
||||
|
||||
Beyond charts, the standard dashboard can be broken down into three key areas:
|
||||
|
||||
1. [**Sections**](#sections)
|
||||
2. [**Menus/submenus**](#menus)
|
||||
3. [**Nodes menu**](#nodes-menu)
|
||||
2. [**Metrics menus/submenus**](#metrics-menus)
|
||||
3. [**Cloud menus: Spaces, War Rooms, and Visited nodes)**](#cloud-menus-spaces-war-rooms-and-visited-nodes)
|
||||
|
||||
|
||||
dashboard](https://user-images.githubusercontent.com/1153921/80834497-ac9c2380-8ba5-11ea-83c4-b323dd89557f.png)
|
||||
|
||||
### Sections
|
||||
|
||||
|
|
@ -58,56 +53,41 @@ broken down into [contexts](/web/README.md#contexts) and
|
|||
An example of the **Memory** section on a Linux desktop system.
|
||||
|
||||
|
||||
dashboard](https://user-images.githubusercontent.com/1153921/80834530-bcb40300-8ba5-11ea-9219-cd554577844e.png)
|
||||
|
||||
All sections and their associated charts appear on a single "page," so all you
|
||||
need to do to view different sections is scroll up and down the page. But it's
|
||||
usually quicker to use the [menus](#menus).
|
||||
usually quicker to use the [menus](#metrics-menus).
|
||||
|
||||
### Menus
|
||||
### Metrics menus
|
||||
|
||||
**Menus** appears on the right-hand side of the standard dashboard. Netdata
|
||||
generates a menu for each section, and menus link to the section they're
|
||||
associated with.
|
||||
**Metrics menus** appears on the right-hand side of the standard dashboard. Netdata generates a menu for each section,
|
||||
and menus link to the section they're associated with.
|
||||
|
||||
|
||||
|
||||
|
||||
Most menu items will contain several **submenu** entries, which represent any
|
||||
Most metrics menu items will contain several **submenu** entries, which represent any
|
||||
[families](/web/README.md#families) from that section. Netdata automatically
|
||||
generates these submenu entries.
|
||||
|
||||
Here's a **Disks** menu with several submenu entries for each disk drive and
|
||||
partition Netdata recognizes.
|
||||
|
||||
|
||||
|
||||
|
||||
### Nodes menu
|
||||
### Cloud menus (Spaces, War Rooms, and Visited nodes)
|
||||
|
||||
The nodes menu appears in the top-left corner of the standard dashboard and is
|
||||
labeled with the hostname of the system Netdata is monitoring.
|
||||
The dashboard also features a menu related to Cloud functionality. You can view your existing Spaces or create new ones
|
||||
via the vertical column of boxes. This menu also displays the name of your current Space, shows a list of any War Rooms
|
||||
you've added you your Space, and lists your Visited nodes. If you click on a War Room's name, the dashboard redirects
|
||||
you to the Netdata Cloud web interface.
|
||||
|
||||
Clicking on it will display a drop-down menu of any nodes you might have
|
||||
connected via the [Netdata registry](/registry/README.md). By default, you'll find
|
||||
nothing under the **My nodes** heading, but you can try out any of the demo
|
||||
Netdata nodes to see how the nodes menu works.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you add nodes via [Netdata Cloud](/docs/netdata-cloud/README.md) or a [private
|
||||
registry](/registry/README.md#run-your-own-registry), you will see them appear under
|
||||
the **My nodes** heading.
|
||||
|
||||
|
||||
|
||||
The nodes menu will also show the master netdata node and all slave nodes
|
||||
streaming to that master, if you have [configured streaming](/streaming/README.md).
|
||||
|
||||
|
||||
If you want to know more about how Cloud populates this menu, and the Agent-Cloud integration at a high level, see our
|
||||
document on [using the Agent with Netdata Cloud](/docs/agent-cloud.md).
|
||||
|
||||
## Customizing the standard dashboard
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue