opensourcemirror
/
netdata
mirror of https://github.com/netdata/netdata.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Reorg learn 0226 (#14610) 

* Reorg getting started

* Streaming

* Remove blanks

* Fix up to cloud alerts
This commit is contained in:
Chris Akritidis 2023-02-26 09:38:33 -08:00 committed by GitHub
parent c906ddafe6
commit 20745bf78b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
34 changed files with 334 additions and 770 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

111
daemon/README.md
View File

@ -1,101 +1,10 @@
<!--
title: "Netdata daemon"
date: "2020-04-29"
custom_edit_url: "https://github.com/netdata/netdata/edit/master/daemon/README.md"
sidebar_label: "Netdata daemon"
learn_status: "Published"
learn_rel_path: "Operations"
-->
# Netdata daemon
## Starting netdata
The Netdata daemon is practically a synonym for the Netdata Agent, as it controls its
entire operation. We support various methods to
[start, stop, or restart the daemon](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md).
- You can start Netdata by executing it with `/usr/sbin/netdata` (the installer will also start it).
- You can stop Netdata by killing it with `killall netdata`. You can stop and start Netdata at any point. When
exiting, the [database engine](https://github.com/netdata/netdata/blob/master/database/engine/README.md) saves metrics to `/var/cache/netdata/dbengine/` so that
it can continue when started again.
Access to the web site, for all graphs, is by default on port `19999`, so go to:
```sh
http://127.0.0.1:19999/
```
You can get the running config file at any time, by accessing `http://127.0.0.1:19999/netdata.conf`.
### Starting Netdata at boot
In the `system` directory you can find scripts and configurations for the
various distros.
#### systemd
The installer already installs `netdata.service` if it detects a systemd system.
To install `netdata.service` by hand, run:
```sh
# stop Netdata
killall netdata
# copy netdata.service to systemd
cp system/netdata.service /etc/systemd/system/
# let systemd know there is a new service
systemctl daemon-reload
# enable Netdata at boot
systemctl enable netdata
# start Netdata
systemctl start netdata
```
#### init.d
In the system directory you can find `netdata-lsb`. Copy it to the proper place according to your distribution
documentation. For Ubuntu, this can be done via running the following commands as root.
```sh
# copy the Netdata startup file to /etc/init.d
cp system/netdata-lsb /etc/init.d/netdata
# make sure it is executable
chmod +x /etc/init.d/netdata
# enable it
update-rc.d netdata defaults
```
#### openrc (gentoo)
In the `system` directory you can find `netdata-openrc`. Copy it to the proper
place according to your distribution documentation.
#### CentOS / Red Hat Enterprise Linux
For older versions of RHEL/CentOS that don't have systemd, an init script is included in the system directory. This can
be installed by running the following commands as root.
```sh
# copy the Netdata startup file to /etc/init.d
cp system/netdata-init-d /etc/init.d/netdata
# make sure it is executable
chmod +x /etc/init.d/netdata
# enable it
chkconfig --add netdata
```
_There have been some recent work on the init script, see PR
<https://github.com/netdata/netdata/pull/403>_
#### other systems
You can start Netdata by running it from `/etc/rc.local` or equivalent.
This document provides some basic information on the command line options, log files, and how to debug and troubleshoot
## Command line options
@ -302,7 +211,7 @@ You can use the following:
For more information see `man sched`.
### scheduling priority for `rr` and `fifo`
### Scheduling priority for `rr` and `fifo`
Once the policy is set to one of `rr` or `fifo`, the following will appear:
@ -323,7 +232,7 @@ When the policy is set to `other`, `nice`, or `batch`, the following will appear
process nice level = 19
```
## scheduling settings and systemd
## Scheduling settings and systemd
Netdata will not be able to set its scheduling policy and priority to more important values when it is started as the
`netdata` user (systemd case).
@ -471,7 +380,7 @@ will contain the messages.
> Do not forget to disable tracing (`debug flags = 0`) when you are done tracing. The file `debug.log` can grow too
> fast.
### compiling Netdata with debugging
### Compiling Netdata with debugging
To compile Netdata with debugging, use this:
@ -486,7 +395,7 @@ CFLAGS="-O1 -ggdb -DNETDATA_INTERNAL_CHECKS=1" ./netdata-installer.sh
The above will compile and install Netdata with debugging info embedded. You can now use `debug flags` to set the
section(s) you need to trace.
### debugging crashes
### Debugging crashes
We have made the most to make Netdata crash free. If however, Netdata crashes on your system, it would be very helpful
to provide stack traces of the crash. Without them, is will be almost impossible to find the issue (the code base is
@ -514,7 +423,7 @@ Run the following command and post the output on a github issue.
gdb $(which netdata) /path/to/core/dump
```
### you can reproduce a Netdata crash on your system
### You can reproduce a Netdata crash on your system
> you need to have Netdata compiled with debugging info for this to work (check above)
@ -526,5 +435,3 @@ valgrind $(which netdata) -D
Netdata will start and it will be a lot slower. Now reproduce the crash and `valgrind` will dump on your console the
stack trace. Open a new github issue and post the output.

6
database/README.md
View File

@ -42,13 +42,13 @@ The default mode `[db].mode = dbengine` has been designed to scale for longer re
for parent Agents in the _Parent - Child_ setups
The other available database modes are designed to minimize resource utilization and should only be considered on
[Parent - Child](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md) setups at the children side and only when the
[Parent - Child](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md) setups at the children side and only when the
resource constraints are very strict.
So,
- On a single node setup, use `[db].mode = dbengine`.
- On a [Parent - Child](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md) setup, use `[db].mode = dbengine` on the
- On a [Parent - Child](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md) setup, use `[db].mode = dbengine` on the
parent to increase retention, a more resource efficient mode like, `dbengine` with light retention settings, and
`save`, `ram` or `none` modes for the children to minimize resource utilization.
@ -68,7 +68,7 @@ Metrics retention is controlled only by the disk space allocated to storing metr
CPU required by the agent to query longer timeframes.
Since Netdata Agents usually run on the edge, on production systems, Netdata Agent **parents** should be considered.
When having a [**parent - child**](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md) setup, the child (the
When having a [**parent - child**](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md) setup, the child (the
Netdata Agent running on a production system) delegates all of its functions, including longer metrics retention and
querying, to the parent node that can dedicate more resources to this task. A single Netdata Agent parent can centralize
multiple children Netdata Agents (dozens, hundreds, or even thousands depending on its available resources).

19
docs/Running-behind-apache.md
View File

@ -1,13 +1,4 @@
<!--
title: "Netdata via apache's mod_proxy"
custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/Running-behind-apache.md"
sidebar_label: "Netdata via apache's mod_proxy"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Configuration/Secure your nodes"
-->
# Netdata via apache's mod_proxy
# Netdata via Apache's mod_proxy
Below you can find instructions for configuring an apache server to:
@ -38,13 +29,11 @@ Also, enable the rewrite module:
```sh
sudo a2enmod rewrite
```
## Netdata on an existing virtual host
On any **existing** and already **working** apache virtual host, you can redirect requests for URL `/netdata/` to one or more Netdata servers.
### proxy one Netdata, running on the same server apache runs
### Proxy one Netdata, running on the same server apache runs
Add the following on top of any existing virtual host. It will allow you to access Netdata as `http://virtual.host/netdata/`.
@ -74,7 +63,7 @@ Add the following on top of any existing virtual host. It will allow you to acce
</VirtualHost>
```
### proxy multiple Netdata running on multiple servers
### Proxy multiple Netdata running on multiple servers
Add the following on top of any existing virtual host. It will allow you to access multiple Netdata as `http://virtual.host/netdata/HOSTNAME/`, where `HOSTNAME` is the hostname of any other Netdata server you have (to access the `localhost` Netdata, use `http://virtual.host/netdata/localhost/`).
@ -355,7 +344,7 @@ If your apache server is not on localhost, you can set:
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to match against the connection IP address.
## prevent the double access.log
## Prevent the double access.log
apache logs accesses and Netdata logs them too. You can prevent Netdata from generating its access log, by setting this in `/etc/netdata/netdata.conf`:

8
docs/category-overview-pages/deployment-strategies.md
View File

@ -1,4 +1,4 @@
# Netdata Deployment Strategies
# Deployment strategies
Netdata can be used to monitor all kinds of infrastructure, from stand-alone tiny IoT devices to complex hybrid setups
combining on-premise and cloud infrastructure, mixing bare-metal servers, virtual machines and containers.
@ -7,13 +7,13 @@ There are 3 components to structure your Netdata ecosystem:
1. **Netdata Agents**
To monitor the physical or virtual nodes of your infrastructure, including all applications and containers running on them.
Netdata Agents are Open-Source, licensed under GPL v3+.
2. **Netdata Parents**
To create data centralization points within your infrastructure, to offload Netdata Agents functions from your production
systems, to provide high-availability of your data, increased data retention and isolation of your nodes.
Netdata Parents are implemented using the Netdata Agent software. Any Netdata Agent can be an Agent for a node and a Parent
for other Agents, at the same time.
@ -41,7 +41,7 @@ We suggest to do the following configuration changes for production deployments:
2. Offload Netdata Agents running on production systems, using Netdata Parents to take over most of their functions
To free system resources for the production applications running on them and to isolate production systems from the rest
of the world, while at the same time providing increased data retention, data high availability and security.
See [streaming and replication](https://github.com/netdata/netdata/blob/master/streaming/README.md)
3. Use Netdata Cloud to access the dashboards

9
docs/category-overview-pages/installation-overview.md
View File

@ -1,11 +1,4 @@
<!--
title: "Installation"
sidebar_label: "Installation"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/installation-overview.md"
learn_status: "Published"
learn_rel_path: "Installation"
sidebar_position: 5
-->
# Installation
In this category you can find instructions on all the possible ways you can install Netdata on the
[supported platforms](https://github.com/netdata/netdata/blob/master/packaging/PLATFORM_SUPPORT.md).

25
docs/cloud/alerts-notifications/add-discord-notification.md
View File

@ -1,17 +1,8 @@
<!--
title: "Add Discord notification configuration"
sidebar_label: "Add Discord notification configuration"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-discord-notification-configuration.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
learn_docs_purpose: "Instructions on how to add notification configuration for Discord"
-->
# Add Discord notification configuration
From the Netdata Cloud UI, you can manage your space's notification settings and enable the configuration to deliver notifications on Discord.
#### Prerequisites
## Prerequisites
To enable Discord notifications you need:
@ -19,7 +10,7 @@ To enable Discord notifications you need:
- Access to the space as an **administrator**
- Have a Discord server able to receive webhook integrations. For mode details check [how to configure this on Discord](#settings-on-discord)
#### Steps
## Steps
1. Click on the **Space settings** cog (located above your profile icon)
1. Click on the **Notification** tab
@ -35,9 +26,9 @@ To enable Discord notifications you need:
- Webhook URL - URL provided on Discord for the channel you want to receive your notifications. For more details check [how to configure this on Discord](#settings-on-discord)
- Thread name - if the Discord channel is a **Forum channel** you will need to provide the thread name as well
#### Settings on Discord
## Settings on Discord
#### Enable webhook integrations on Discord server
## Enable webhook integrations on Discord server
To enable the webhook integrations on Discord you need:
1. Go to *Integrations** under your **Server Settings
@ -51,9 +42,3 @@ To enable the webhook integrations on Discord you need:
![image](https://user-images.githubusercontent.com/82235632/214092713-d16389e3-080f-4e1c-b150-c0fccbf4570e.png)
For more details please read this article from Discord: [Intro to Webhooks](https://support.discord.com/hc/en-us/articles/228383668).
#### Related topics
- [Alerts Configuration](https://github.com/netdata/netdata/blob/master/health/README.md)
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
- [Manage notification methods](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md)

27
docs/cloud/alerts-notifications/add-pagerduty-notification-configuration.md
View File

@ -1,17 +1,8 @@
<!--
title: "Add PagerDuty notification configuration"
sidebar_label: "Add PagerDuty notification configuration"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-pagerduty-notification-configuration.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
learn_docs_purpose: "Instructions on how to add notification configuration for PagerDuty"
-->
# Add PagerDuty notification configuration
From the Cloud interface, you can manage your space's notification settings and from these you can add a specific configuration to get notifications delivered on PagerDuty.
#### Prerequisites
## Prerequisites
To add PagerDuty notification configurations you need
@ -20,7 +11,7 @@ To add PagerDuty notification configurations you need
- Space needs to be on **Business** plan or higher
- Have a PagerDuty service to receive events, for mode details check [how to configure this on PagerDuty](#settings-on-pagerduty)
#### Steps
## Steps
1. Click on the **Space settings** cog (located above your profile icon)
1. Click on the **Notification** tab
@ -34,9 +25,9 @@ To add PagerDuty notification configurations you need
1. **Integration configuration** are the specific notification integration required settings, which vary by notification method. For PagerDuty:
- Integration Key - is a 32 character key provided by PagerDuty to receive events on your service. For more details check [how to configure this on PagerDuty](#settings-on-pagerduty)
#### Settings on PagerDuty
## Settings on PagerDuty
#### Enable webhook integrations on PagerDuty
## Enable webhook integrations on PagerDuty
To enable the webhook integrations on PagerDuty you need:
1. Create a service to receive events from your services directory page:
@ -49,12 +40,4 @@ To enable the webhook integrations on PagerDuty you need:
1. Once the service is created you will be redirected to its configuration page, where you can copy the **integration key**, that you will need need to add to your notification configuration on Netdata UI:
![image](https://user-images.githubusercontent.com/2930882/214255916-0d2e53d5-87cc-408a-9f5b-0308a3262d5c.png)
#### Related topics
- [Alerts Configuration](https://github.com/netdata/netdata/blob/master/health/README.md)
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
- [Manage notification methods](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md)

24
docs/cloud/alerts-notifications/add-slack-notification-configuration.md
View File

@ -1,17 +1,8 @@
<!--
title: "Add Slack notification configuration"
sidebar_label: "Add Slack notification configuration"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-slack-notification-configuration.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
learn_docs_purpose: "Instructions on how to add notification configuration for Slack"
-->
# Add Slack notification configuration
From the Cloud interface, you can manage your space's notification settings and from these you can add a specific configuration to get notifications delivered on Slack.
#### Prerequisites
## Prerequisites
To add discord notification configurations you need
@ -20,7 +11,7 @@ To add discord notification configurations you need
- Space needs to be on **Business** plan or higher
- Have a Slack app on your workspace to receive the webhooks, for mode details check [how to configure this on Slack](#settings-on-slack)
#### Steps
## Steps
1. Click on the **Space settings** cog (located above your profile icon)
1. Click on the **Notification** tab
@ -34,7 +25,7 @@ To add discord notification configurations you need
1. **Integration configuration** are the specific notification integration required settings, which vary by notification method. For Slack:
- Webhook URL - URL provided on Slack for the channel you want to receive your notifications. For more details check [how to configure this on Slack](#settings-on-slack)
#### Settings on Slack
## Settings on Slack
To enable the webhook integrations on Slack you need:
1. Create an app to receive webhook integrations. Check [Create an app](https://api.slack.com/apps?new_app=1) from Slack documentation for further details
@ -54,10 +45,3 @@ To enable the webhook integrations on Slack you need:
![image](https://user-images.githubusercontent.com/82235632/214104412-13aaeced-1b40-4894-85f6-9db0eb35c584.png)
For more details please check Slacks's article [Incoming webhooks for Slack](https://slack.com/help/articles/115005265063-Incoming-webhooks-for-Slack).
#### Related topics
- [Alerts Configuration](https://github.com/netdata/netdata/blob/master/health/README.md)
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
- [Manage notification methods](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md)

29
docs/cloud/alerts-notifications/add-webhook-notification-configuration.md
View File

@ -1,17 +1,8 @@
<!--
title: "Add webhook notification configuration"
sidebar_label: "Add webhook notification configuration"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-webhook-notification-configuration.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
learn_docs_purpose: "Instructions on how to add notification configuration for webhook"
-->
# Add webhook notification configuration
From the Cloud interface, you can manage your space's notification settings and from these you can add a specific configuration to get notifications delivered on a webhook using a predefined schema.
#### Prerequisites
## Prerequisites
To add discord notification configurations you need
@ -20,7 +11,7 @@ To add discord notification configurations you need
- Space needs to be on **Pro** plan or higher
- Have an app that allows you to receive webhooks following a predefined schema, for mode details check [how to create the webhook service](#webhook-service)
#### Steps
## Steps
1. Click on the **Space settings** cog (located above your profile icon)
1. Click on the **Notification** tab
@ -39,11 +30,11 @@ To add discord notification configurations you need
- Basic - the client sends a request with an Authorization header that includes a base64-encoded string in the format **username:password**. These will settings will be required inputs.
- Bearer - the client sends a request with an Authorization header that includes a **bearer token**. This setting will be a required input.
#### Webhook service
## Webhook service
A webhook integration allows your application to receive real-time alerts from Netdata by sending HTTP requests to a specified URL. In this document, we'll go over the steps to set up a generic webhook integration, including adding headers, and implementing different types of authorization mechanisms.
##### Netdata webhook integration
### Netdata webhook integration
A webhook integration is a way for one service to notify another service about events that occur within it. This is done by sending an HTTP POST request to a specified URL (known as the "webhook URL") when an event occurs.
@ -68,7 +59,7 @@ The notification content sent to the destination service will be a JSON object h
| warning_count | integer | Number of warning alerts currently existing on the same node. |
| alarm_url | string | Netdata Cloud URL for this alarm. |
##### Extra headers
### Extra headers
When setting up a webhook integration, the user can specify a set of headers to be included in the HTTP requests sent to the webhook URL.
@ -78,7 +69,7 @@ By default, the following headers will be sent in the HTTP request
|:-------------------------------:|-----------------------------|
| Content-Type | application/json |
##### Authorization mechanism
### Authorization mechanism
Netdata webhook integration supports 3 different authorization mechanisms:
@ -97,9 +88,3 @@ In basic authorization, the client sends a request with an Authorization header
3. Bearer
In bearer token authorization, the client sends a request with an Authorization header that includes a bearer token. The server then uses this token to authenticate the client. Bearer tokens are typically generated by an authentication service, and are passed to the client after a successful authentication. If this method is selected, the user can set the token to be used for connecting to the destination service.
#### Related topics
- [Alerts Configuration](https://github.com/netdata/netdata/blob/master/health/README.md)
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
- [Manage notification methods](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md)

32
docs/cloud/alerts-notifications/manage-notification-methods.md
View File

@ -1,25 +1,17 @@
<!--
title: "Manage notification methods"
sidebar_label: "Manage notification methods"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
learn_docs_purpose: "Instructions on how to manage notification methods"
-->
# Manage notification methods
From the Cloud interface, you can manage your space's notification settings as well as allow users to personalize their notifications setting
### Manage space notification settings
## Manage space notification settings
#### Prerequisites
### Prerequisites
To manage space notification settings, you will need the following:
- A Netdata Cloud account
- Access to the space as an **administrator**
#### Available actions per notification methods based on service level
### Available actions per notification methods based on service level
| **Action** | **Personal service level** | **System service level** |
| :- | :-: | :-: |
@ -32,7 +24,7 @@ Notes:
* For Netadata provided ones you can't delete the existing notification method configuration.
* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#service-classification))
#### Steps
### Steps
1. Click on the **Space settings** cog (located above your profile icon)
1. Click on the **Notification** tab
@ -53,9 +45,9 @@ Notes:
1. **Delete an existing** notification method configuartion. Netdata provided ones can't be deleted, e.g. Email
- Use the trash icon to delete your configuration
### Manage user notification settings
## Manage user notification settings
#### Prerequisites
### Prerequisites
To manage user specific notification settings, you will need the following:
@ -64,7 +56,7 @@ To manage user specific notification settings, you will need the following:
Note: If an administrator has disabled a Personal [service level](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#service-level) notification method this will override any user specific setting.
#### Steps
### Steps
1. Click on the **User notification settings** shortcut on top of the help button
1. You are presented with:
@ -78,11 +70,3 @@ Note: If an administrator has disabled a Personal [service level](https://github
1. **Activate notifications** for a room you aren't a member of
- From the **All Rooms** tab click on the Join button for the room(s) you want
#### Related topics
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
- [Alerts Configuration](https://github.com/netdata/netdata/blob/master/health/README.md)
- [Add webhook notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-webhook-notification-configuration.md)
- [Add Discord notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-discord-notification.md)
- [Add Slack notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-slack-notification-configuration.md)
- [Add PagerDuty notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-pagerduty-notification-configuration.md)

35
docs/cloud/alerts-notifications/notifications.md
View File

@ -1,11 +1,4 @@
<!--
title: "Cloud alert notifications"
description: "Configure Netdata Cloud to send notifications to your team whenever any node on your infrastructure triggers an alert threshold."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md"
sidebar_label: "Cloud alert notifications"
learn_status: "Published"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
-->
# Cloud alert notifications
import Callout from '@site/src/components/Callout'
@ -14,7 +7,7 @@ unreachable state. By enabling notifications, you ensure no alert, on any node i
you or your team.
Having this information centralized helps you:
* Have a clear view of the health across your infrastructure, [seeing all a alerts in one place](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/view-active-alerts.md)
* Have a clear view of the health across your infrastructure, seeing all alerts in one place.
* Easily [setup your alert notification process](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md):
methods to use and where to use them, filtering rules, etc.
* Quickly troubleshoot using [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md)
@ -126,27 +119,3 @@ within Cloud's embedded dashboards.
Here's an example email notification for the `ram_available` chart, which is in a critical state:
![Screenshot of an alarm notification email from Netdata Cloud](https://user-images.githubusercontent.com/1153921/87461878-e933c480-c5c3-11ea-870b-affdb0801854.png)
## What's next?
Netdata Cloud's alarm notifications feature leverages the alarms configuration on each node in your infrastructure. If
you'd like to tweak any of these alarms, or even add new ones based on your needs, read our [Health
configuration documentation](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md).
You can also [view active alarms](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/view-active-alerts.md) in Netdata Cloud for an instant
visualization of the health of your infrastructure.
### Related Topics
#### **Related Concepts**
- [Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md)
- [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md)
- [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/anomaly-advisor.md)
#### Related Tasks
- [View Active alarms](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/view-active-alerts.md)
- [Manage notification methods](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/manage-notification-methods.md)
- [Add webhook notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-webhook-notification-configuration.md)
- [Add Discord notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-discord-notification.md)
- [Add Slack notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-slack-notification-configuration.md)
- [Add PagerDuty notification configuration](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/add-pagerduty-notification-configuration.md)

46
docs/cloud/alerts-notifications/smartboard.md
View File

@ -1,46 +0,0 @@
<!--
title: "Alerts smartboard"
description: ""
type: "reference"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/smartboard.md"
sidebar_label: "Alerts smartboard"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Integrations/Notify/Cloud alert notifications"
-->
The Alerts view gives you a high level of availability and performance information for every node you're
monitoring with Netdata Cloud. We expect it to become the "home base" for many Netdata Cloud users who want to instantly
understand what's going on with their infrastructure and exactly where issues might be.
The Alerts view is available entirely for free to all users and for any number of nodes.
## Alerts table and filtering
The Alerts view shows all active alerts in your War Room, including the alert's name, the most recent value, a
timestamp of when it became active, and the relevant node.
You can use the checkboxes in the filter pane on the right side of the screen to filter the alerts displayed in the
table
by Status, Class, Type & Componenet, Role, Operating System, or Node.
Click on any of the alert names to see the alert.
## View active alerts
In the `Active` subtab, you can see exactly how many **critical** and **warning** alerts are active across your nodes.
## View configured alerts
You can view all the configured alerts on all the agents that belong to a War Room in the `Alert Configurations` subtab.
From within the Alerts view, you can click the `Alert Configurations` subtab to see a high level view of the states of
the alerts on the nodes within this War Room and drill down to the node level where each alert is configured with their
latest status.

49
docs/cloud/alerts-notifications/view-active-alerts.md
View File

@ -1,49 +0,0 @@
# View active alerts
Netdata Cloud receives information about active alerts on individual nodes in your infrastructure and updates the
interface based on those status changes.
Netdata Cloud doesn't produce alerts itself but rather receives and aggregates alerts from each node in your
infrastructure based on their configuration. Every node comes with hundreds of pre-configured alerts that have been
tested by Netdata's community of DevOps engineers and SREs, but you may want to customize existing alerts or create new
ones entirely.
Read our documentation on [health alerts](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md) to
learn how to tweak existing alerts or create new
health entities based on the specific needs of your infrastructure. By taking charge of alert configuration, you'll
ensure Netdata Cloud always delivers the most relevant alerts about the well-being of your nodes.
## View all active alerts
The [Alerts Smartboard](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/smartboard.md)
provides a high-level interface for viewing the number of critical or warning alerts and where they are in your
infrastructure.
![The Alerts Smartboard](https://user-images.githubusercontent.com/1153921/119025635-2fcb1b80-b959-11eb-9fdb-7f1a082f43c5.png)
Click on the **Alerts** tab in any War Room to open the Smartboard. Alternatively, click on any of the alert badges in
the [Nodes view](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/nodes.md) to jump to the Alerts
Smartboard.
From here, filter active alerts using the **critical** or **warning** boxes, or hover over a box in
the [nodes map](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/smartboard.md#nodes-map)
to see a
popup node-specific alert information.
## View alerts in context with charts
If you click on any of the alerts, either in a nodes map popup or the alerts table, Netdata Cloud navigates you to the
single-node dashboard and scrolls to the relevant chart. Netdata Cloud also draws a highlight and the value at the
moment your node triggered this alert.
![An alert in context with charts and dimensions](https://user-images.githubusercontent.com/1153921/119039593-4a0cf580-b969-11eb-840c-4ecb123df9f5.png)
You can
then [highlight this area](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md#highlight)
with `Alt/⌘ + mouse selection` to highlight the alerted timeframe while you explore other charts for root cause
analysis.
Or, select the area and
run [Metric Correlations](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md) to
filter the single-node
dashboard to only those charts most likely to be connected to the alert.

10
docs/cloud/data-privacy.md
View File

@ -1,12 +1,4 @@
<!--
title: "Data privacy in the Netdata Cloud"
description: "Keeping your data safe and secure is our priority.Netdata never stores your personal information in the Netdata Cloud."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/data-privacy.md"
sidebar_label: "Data privacy in the Netdata Cloud"
learn_status: "Published"
learn_topic_type: "Concepts"
learn_rel_path: "Concepts"
-->
# Data privacy in Netdata Cloud
[Data privacy](https://netdata.cloud/privacy/) is very important to us. We firmly believe that your data belongs to
you. This is why **we don't store any metric data in Netdata Cloud**.

12
docs/cloud/manage/invite-your-team.md
View File

@ -1,14 +1,4 @@
<!--
title: "Invite your team"
description: >-
"Invite your entire SRE, DevOPs, or ITOps team to Netdata Cloud to give everyone insights into your
infrastructure from a single pane of glass."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/invite-your-team.md"
sidebar_label: "Invite your team"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# Invite your team
Invite new users to your Space by clicking on **Invite Users** in
the [Space](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md) management area.

37
docs/cloud/manage/role-based-access.md
View File

@ -1,17 +1,8 @@
<!--
title: "Role-Based Access model"
sidebar_label: "Role-Based Access model"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Concepts"
learn_rel_path: "Concepts"
learn_docs_purpose: "Explanation of Netdata roles and permissions linked to them"
-->
# Role-Based Access model"
Netdata Cloud's role-based-access mechanism allows you to control what functionalities in the app users can access. Each user can be assigned only one role, which fully specifies all the capabilities they are afforded.
#### What roles are available?
## What roles are available?
With the advent of the paid plans we revamped the roles to cover needs expressed by Netdata users, like providing more limited access to their customers, or
being able to join any room. We also aligned the offered roles to the target audience of each plan. The end result is the following:
@ -25,15 +16,15 @@ being able to join any room. We also aligned the offered roles to the target aud
| **Billing**<p>This role is for users that need to manage billing options and see invoices, with no further access to the system.</p> | - | - | :heavy_check_mark: | - |
| **Member** ⚠️ Legacy role<p>This role allows users to manage War Rooms and invite fellow Member teammates.</p><p>These users cannot see all War Rooms in the Space but can see all Nodes since they are always on the _All Nodes_ room.</p>| - | - | - | :heavy_check_mark: |
#### What happens to the previous Member role?
## What happens to the previous Member role?
We will maintain a Early Bird plan for existing users, which will continue to provide access to the Member role.
#### Which functionalities are available for each role?
## Which functionalities are available for each role?
In more detail, you can find on the following tables which functionalities are available for each role on each domain.
##### Space Management
### Space Management
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |
@ -43,7 +34,7 @@ In more detail, you can find on the following tables which functionalities are a
| Change name | :heavy_check_mark: | - | - | - | - | - |
| Change description | :heavy_check_mark: | - | - | - | - | - |
##### Node Management
### Node Management
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -51,7 +42,7 @@ In more detail, you can find on the following tables which functionalities are a
| Connect Node to Space | :heavy_check_mark: | - | - | - | - | - | - |
| Delete Node from Space | :heavy_check_mark: | - | - | - | - | - | - |
##### User Management
### User Management
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -69,7 +60,7 @@ In more detail, you can find on the following tables which functionalities are a
| Invite existing user to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | User already invited to the Space |
| Remove user from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | |
##### Room Management
### Room Management
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -83,7 +74,7 @@ In more detail, you can find on the following tables which functionalities are a
| Add existing Nodes to Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | Node already connected to the Space |
| Remove Nodes from Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | :heavy_check_mark: | |
##### Notifications Management
### Notifications Management
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -97,7 +88,7 @@ In more detail, you can find on the following tables which functionalities are a
Notes:
* Enable, Edit and Add actions over specific notification methods will only be allowed if your plan has access to those ([service classification](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#service-classification))
##### Dashboards
### Dashboards
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |
@ -108,7 +99,7 @@ Notes:
| Delete any dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | :heavy_check_mark: |
| Delete own dashboard in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: |
##### Functions
### Functions
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -117,14 +108,14 @@ Notes:
| Run read-only function in Room | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
| Run sensitive function in Room | :heavy_check_mark: | :heavy_check_mark: | - | - | - | - | There isn't any function on this category yet, so subject to change. |
##### Events feed
### Events feed
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
| See Alert or Topology events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | :heavy_check_mark: | |
| See Auditing events | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | - | - | These are coming soon, not currently available |
##### Billing
### Billing
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** | Notes |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: | :-- |
@ -134,7 +125,7 @@ Notes:
| Manage payment methods | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
| Update billing email | :heavy_check_mark: | - | - | - | :heavy_check_mark: | - | |
##### Other permissions
### Other permissions
| **Functionality** | **Administrator** | **Manager** | **Troubleshooter** | **Observer** | **Billing** | **Member** |
| :-- | :--: | :--: | :--: | :--: | :--: | :--: |

15
docs/cloud/manage/sign-in.md
View File

@ -1,12 +1,4 @@
<!--
title: "Sign in with email, Google, or GitHub"
description: "Learn how signing in to Cloud works via one of our three authentication methods, plus some tips if you're having trouble signing in."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/sign-in.md"
sidebar_label: "Sign in with email, Google, or GitHub"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# Sign in with email, Google, or GitHub
You can [sign in to Netdata](https://app.netdata.cloud/sign-in?cloudRoute=spaces?utm_source=docs&utm_content=sign_in_button_first_section) through one of three methods: email, Google, or GitHub. Email uses a
time-sensitive link that authenticates your browser, and Google/GitHub both use OAuth to associate your email address
@ -81,8 +73,3 @@ with `user2@example.com`, Netdata Cloud creates a new account and begins the onb
It is not currently possible to link an account created with `user@example.com` to a Google account associated with
`user2@example.com`.
## What's next?
If you haven't already onboarded to Netdata Cloud and connected your first nodes, visit
the [Get Started section of our documentation](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md).

10
docs/cloud/manage/themes.md
View File

@ -1,12 +1,4 @@
<!--
title: "Choose your Netdata Cloud theme"
description: "Switch between Light and Dark themes in Netdata Cloud to match your personal visualization preferences."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/themes.md"
sidebar_label: "Choose your Netdata Cloud theme"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# Choose your Netdata Cloud theme
The Dark theme is the default for all new Netdata Cloud accounts.

11
docs/cloud/manage/view-plan-billing.md
View File

@ -1,13 +1,4 @@
<!--
title: "View Plan & Billing"
sidebar_label: "View Plan & Billing"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md"
sidebar_position: "1"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
learn_docs_purpose: "How to check details on your space plan and billing"
-->
# View Plan & Billing
From the Cloud interface, you can view and manage your space's plan and billing settings, and see the space's usage in terms of running nodes.
To view and manage some specific settings, related to billing options and invoices, you'll be redirected to our billing provider Customer Portal.

12
docs/cloud/spaces.md
View File

@ -1,14 +1,4 @@
<!--
title: "Spaces"
description: >-
"Organize your infrastructure monitoring on Netdata Cloud by creating Spaces, then groupingyour
Agent-monitored nodes."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md"
sidebar_label: "Spaces"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# Spaces
A Space is a high-level container. It's a collaboration space where you can organize team members, access levels and the
nodes you want to monitor.

6
docs/cloud/visualize/overview.md
View File

@ -1,4 +1,4 @@
# Home, Overview and Single Node view
# Home, overview and single node views
## Home
@ -7,7 +7,7 @@ The Home tab provides a predefined dashboard of relevant information about entit
This tab will automatically present summarized information in an easily digestible display. You can see information about your
nodes, data collection and retention stats, alerts, users and dashboards.
## Overview and Single Node view
## Overview and single node view
The Overview tab is another great way to monitor infrastructure using Netdata Cloud. While the interface might look
similar to local dashboards served by an Agent Overview uses **composite charts**.
@ -19,7 +19,7 @@ you can see your infrastructure from a single pane of glass, discover trends or
The Single Node view dashboard is exactly the same as the Overview, but with a hard-coded filter to only show
a single node.
### Chart Navigation Menu
### Chart navigation Menu
Netdata Cloud uses a similar menu to local Agent dashboards, with sections
and sub-menus aggregated from every contributing node. For example, even if only two nodes actively collect from and

12
docs/cloud/war-rooms.md
View File

@ -1,14 +1,4 @@
<!--
title: "War Rooms"
description: >-
"Netdata Cloud uses War Rooms to group related nodes and create insightful compositedashboards based on
their aggregate health and performance."
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md"
sidebar_label: "War Rooms"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# War rooms
War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and
visualizations.

91
docs/configure/start-stop-restart.md
View File

@ -1,20 +1,10 @@
<!--
title: "Start, stop, or restart the Netdata Agent"
description: "Manage the Netdata Agent daemon, load configuration changes, and troubleshoot stuck processes on systemd and non-systemd nodes."
custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/configure/start-stop-restart.md"
sidebar_label: "Start, stop, or restart the Netdata Agent"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Operations"
-->
# Start, stop, or restart the Netdata Agent
When you install the Netdata Agent, the [daemon](https://github.com/netdata/netdata/blob/master/daemon/README.md) is configured to start at boot and stop and
restart/shutdown.
When you install the Netdata Agent, the [daemon](https://github.com/netdata/netdata/blob/master/daemon/README.md) is
configured to start at boot and stop and restart/shutdown.
You will most often need to _restart_ the Agent to load new or editing configuration files. [Health
configuration](#reload-health-configuration) files are the only exception, as they can be reloaded without restarting
You will most often need to _restart_ the Agent to load new or editing configuration files.
[Health configuration](#reload-health-configuration) files are the only exception, as they can be reloaded without restarting
the entire Agent.
Stopping or restarting the Netdata Agent will cause gaps in stored metrics until the `netdata` process initiates
@ -81,3 +71,76 @@ ps aux| grep netdata
The output of `ps aux` should show no `netdata` or associated processes running. You can now start the Netdata Agent
again with `service netdata start`, or the appropriate method for your system.
## Starting Netdata at boot
In the `system` directory you can find scripts and configurations for the
various distros.
### systemd
The installer already installs `netdata.service` if it detects a systemd system.
To install `netdata.service` by hand, run:
```sh
# stop Netdata
killall netdata
# copy netdata.service to systemd
cp system/netdata.service /etc/systemd/system/
# let systemd know there is a new service
systemctl daemon-reload
# enable Netdata at boot
systemctl enable netdata
# start Netdata
systemctl start netdata
```
### init.d
In the system directory you can find `netdata-lsb`. Copy it to the proper place according to your distribution
documentation. For Ubuntu, this can be done via running the following commands as root.
```sh
# copy the Netdata startup file to /etc/init.d
cp system/netdata-lsb /etc/init.d/netdata
# make sure it is executable
chmod +x /etc/init.d/netdata
# enable it
update-rc.d netdata defaults
```
### openrc (gentoo)
In the `system` directory you can find `netdata-openrc`. Copy it to the proper
place according to your distribution documentation.
### CentOS / Red Hat Enterprise Linux
For older versions of RHEL/CentOS that don't have systemd, an init script is included in the system directory. This can
be installed by running the following commands as root.
```sh
# copy the Netdata startup file to /etc/init.d
cp system/netdata-init-d /etc/init.d/netdata
# make sure it is executable
chmod +x /etc/init.d/netdata
# enable it
chkconfig --add netdata
```
_There have been some recent work on the init script, see PR
<https://github.com/netdata/netdata/pull/403>_
### other systems
You can start Netdata by running it from `/etc/rc.local` or equivalent.

89
docs/dashboard/visualization-date-and-time-controls.md
View File

@ -1,18 +1,28 @@
<!--
title: "Visualization date and time controls"
description: "Netdata's dashboard features powerful date visualization controls that include a time control (play, pause, force play), a timezone selector and a rich date and timeframe selector, with useful defaults and rich customization, to help you narrow your focus when troubleshooting issues or anomalies."
type: "how-to"
custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/dashboard/visualization-date-and-time-controls.md"
sidebar_label: "Visualization date and time controls"
learn_status: "Published"
learn_topic_type: "Concepts"
learn_rel_path: "Concepts"
-->
# Visualization date and time controls
## Time controls
The time control provides you the following options: **Play**, **Pause** and **Force Play**.
* **Play** - the content of the page will be automatically refreshed while this is in the foreground
* **Pause** - the content of the page isn't refreshed due to a manual request to pause it or, for example, when your investigating data on a
chart (cursor is on top of a chart)
* **Force Play** - the content of the page will be automatically refreshed even if this is in the background
With this, we aim to bring more clarity and allow you to distinguish if the content you are looking at is live or historical and also allow you
to always refresh the content of the page when the tabs are in the background.
Main use cases for **Force Play**:
* You use a terminal or deployment tools to do changes in your infra and want to see immediately, Netdata is in the background, displaying the impact
of these changes
* You want to have Netdata on the background, example displayed on a TV, to constantly see metrics through dashboards or to watch the alert
status
![The time control with Play, Pause and Force Play](https://user-images.githubusercontent.com/82235632/129206460-03c47d0d-1a5b-428a-b972-473718b74bdb.png)
## Date and time selector
The date and time selector allows you to change the visible timeframe and change the timezone used in the interface.
### Pick timeframes to visualize
While [panning through time and zooming in/out](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) from charts it is helpful when
@ -56,40 +66,7 @@ minutes, hours, days, or months. Enter a number and choose the appropriate unit
Use the calendar to select multiple days. Click on a date to begin the timeframe selection, then an ending date. The
timeframe begins at noon on the beginning and end dates. Click **Apply** to see your selected multi-day timeframe.
## Time controls
The time control provides you the following options: **Play**, **Pause** and **Force Play**.
* **Play** - the content of the page will be automatically refreshed while this is in the foreground
* **Pause** - the content of the page isn't refreshed due to a manual request to pause it or, for example, when your investigating data on a
chart (cursor is on top of a chart)
* **Force Play** - the content of the page will be automatically refreshed even if this is in the background
With this, we aim to bring more clarity and allow you to distinguish if the content you are looking at is live or historical and also allow you
to always refresh the content of the page when the tabs are in the background.
Main use cases for **Force Play**:
* You use a terminal or deployment tools to do changes in your infra and want to see immediately, Netdata is in the background, displaying the impact
of these changes
* You want to have Netdata on the background, example displayed on a TV, to constantly see metrics through dashboards or to watch the alert
status
![The time control with Play, Pause and
Force Play](https://user-images.githubusercontent.com/82235632/129206460-03c47d0d-1a5b-428a-b972-473718b74bdb.png)
## Timezone selector
With the timezone selector, you have the ability to change the timezone on Netdata Cloud. More often than not teams are
distributed in different timezones and they need to collaborate.
Our goal is to make it easier for you and your teams to troubleshoot based on your timezone preference and communicate easily
with varying timezones and timeframes without the need to be concerned about their specificity.
<img width="437" alt="Untitled1" src="https://user-images.githubusercontent.com/43294513/216628390-c3bd1cd2-349d-4523-b8d3-c7e68395f670.png"/>
When you change the timezone all the date and time fields will be updated to be displayed according to the specified timezone, this goes from
charts to alerts information and across the Netdata Cloud.
## Caveats and considerations
#### Caveats and considerations
**Longer timeframes will decrease metrics granularity**. At the default timeframe, based on your browser viewport, each
"tick" on charts represents one second. If you select a timeframe of 6 hours, each tick represents the _average_ value
@ -100,26 +77,14 @@ time-series database (TSDB) to store as many metrics as it can within a specific
storage is 256 MiB, which should be enough for 1-3 days of historical metrics. If you navigate back to a timeframe
beyond stored historical metrics, you'll see this message:
![Screenshot of reaching the end of historical metrics
storage](https://user-images.githubusercontent.com/1153921/114207597-63a23280-9911-11eb-863d-4d2f75b030b4.png)
![Screenshot of reaching the end of historical metrics storage](https://user-images.githubusercontent.com/1153921/114207597-63a23280-9911-11eb-863d-4d2f75b030b4.png)
At any time, [configure the internal TSDB's storage capacity](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) to expand your
depth of historical metrics.
## What's next?
### Timezone selector
One useful next step after selecting a timeframe is [exporting the
metrics](https://github.com/netdata/netdata/blob/master/docs/dashboard/import-export-print-snapshot.md) into a snapshot file, which can then be shared and imported
into any other Netdata dashboard.
The default timezone used in all date and time fields in Netdata Cloud comes from your browser. To change it, open the
date and time selector and use the control displayed here:
There are also many ways to [customize](https://github.com/netdata/netdata/blob/master/docs/dashboard/customize.md) the standard dashboard experience, from changing
the theme to editing the text that accompanies every section of charts.
## Further reading & related information
- Dashboard
- [How the dashboard works](https://github.com/netdata/netdata/blob/master/docs/dashboard/how-dashboard-works.md)
- [Interact with charts](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md)
- [Chart dimensions, contexts, and families](https://github.com/netdata/netdata/blob/master/docs/dashboard/dimensions-contexts-families.md)
- [Import, export, and print a snapshot](https://github.com/netdata/netdata/blob/master/docs/dashboard/import-export-print-snapshot.md)
- [Customize the standard dashboard](https://github.com/netdata/netdata/blob/master/docs/dashboard/customize.md)
<img alt="Untitled1" src="https://user-images.githubusercontent.com/43294513/216628390-c3bd1cd2-349d-4523-b8d3-c7e68395f670.png"/>

120
docs/metrics-storage-management/enable-streaming.md
View File

@ -1,28 +1,75 @@
<!--
title: "Enable streaming between nodes"
description: >-
"With metrics streaming enabled, you can not only replicate metrics data
into a second database, but also view dashboards and trigger alarm notifications
for multiple nodes in parallel."
type: "how-to"
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md"
sidebar_label: "Enable streaming between nodes"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Configuration"
-->
# How metrics streaming works
# Enable streaming between nodes
Each node running Netdata can stream the metrics it collects, in real time, to another node. Streaming allows you to
replicate metrics data across multiple nodes, or centralize all your metrics data into a single time-series database
(TSDB).
When one node streams metrics to another, the node receiving metrics can visualize them on the dashboard, run health checks to
[trigger alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md) and
[send notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md), and
[export](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) all metrics to an external TSDB. When Netdata streams metrics to another
Netdata, the receiving one is able to perform everything a Netdata instance is capable of.
Streaming lets you decide exactly how you want to store and maintain metrics data. While we believe Netdata's
[distributed architecture](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md) is
ideal for speed and scale, streaming provides centralization options and high data availability.
This document will get you started quickly with streaming. More advanced concepts and suggested production deployments
can be found in the [streaming and replication reference](https://github.com/netdata/netdata/blob/master/streaming/README.md).
## Streaming basics
There are three types of nodes in Netdata's streaming ecosystem.
- **Parent**: A node, running Netdata, that receives streamed metric data.
- **Child**: A node, running Netdata, that streams metric data to one or more parent.
- **Proxy**: A node, running Netdata, that receives metric data from a child and "forwards" them on to a
separate parent node.
Netdata uses API keys, which are just random GUIDs, to authorize the communication between child and parent nodes. We
recommend using `uuidgen` for generating API keys, which can then be used across any number of streaming connections.
Or, you can generate unique API keys for each parent-child relationship.
Once the parent node authorizes the child's API key, the child can start streaming metrics.
It's important to note that the streaming connection uses TCP, UDP, or Unix sockets, _not HTTP_. To proxy streaming
metrics, you need to use a proxy that tunnels [OSI layer 4-7
traffic](https://en.wikipedia.org/wiki/OSI_model#Layer_4:_Transport_Layer) without interfering with it, such as
[SOCKS](https://en.wikipedia.org/wiki/SOCKS) or Nginx's
[TCP/UDP load balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/).
## Supported streaming configurations
Netdata supports any combination of parent, child, and proxy nodes that you can imagine. Any node can act as both a
parent, child, or proxy at the same time, sending or receiving streaming metrics from any number of other nodes.
Here are a few example streaming configurations:
- **Headless collector**:
- Child `A`, _without_ a database or web dashboard, streams metrics to parent `B`.
- `A` metrics are only available via the local Agent dashboard for `B`.
- `B` generates alarms for `A`.
- **Replication**:
- Child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
- `A` metrics are available on both local Agent dashboards, and can be stored with the same or different metrics
retention policies.
- Both `A` and `B` generate alarms.
- **Proxy**:
- Child `A`, _with or without_ a database, sends metrics to proxy `C`, also _with or without_ a database. `C` sends
metrics to parent `B`.
- Any node with a database can generate alarms.
## Enable streaming between nodes
The simplest streaming configuration is **replication**, in which a child node streams its metrics in real time to a
parent node, and both nodes retain metrics in their own databases.
To configure replication, you need two nodes, each running Netdata. First you'll first enable streaming on your parent
node, then enable streaming on your child node. When you're finished, you'll be able to see the child node's metrics in
the parent node's dashboard, quickly switch between the two dashboards, and be able to serve [alarm
notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) from either or both nodes.
the parent node's dashboard, quickly switch between the two dashboards, and be able to serve
[alarm notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) from either or both nodes.
## Enable streaming on the parent node
### Enable streaming on the parent node
First, log onto the node that will act as the parent.
@ -58,7 +105,7 @@ simplified version of the configuration, minus the commented lines, looks like t
Save the file and close it, then restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
method](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md) for your system.
## Enable streaming on the child node
### Enable streaming on the child node
Connect to your child node with SSH.
@ -79,7 +126,7 @@ looks like the following:
Save the file and close it, then restart Netdata with `sudo systemctl restart netdata`, or the [appropriate
method](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md) for your system.
## Enable TLS/SSL on streaming (optional)
### Enable TLS/SSL on streaming (optional)
While encrypting the connection between your parent and child nodes is recommended for security, it's not required to
get started. If you're not interested in encryption, skip ahead to [view streamed
@ -119,7 +166,16 @@ self-signed certificates.
Restart both the parent and child nodes with `sudo systemctl restart netdata`, or the [appropriate
method](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md) for your system, to stream encrypted metrics using TLS/SSL.
## View streamed metrics in Netdata's dashboard
### View streamed metrics in Netdata Cloud
In Netdata Cloud you should now be able to see a new parent showing up in the Home tab under "Nodes by data replication".
The replication factor for the child node has now increased to 2, meaning that its data is now highly available.
You don't need to do anything else, as the cloud will automatically prefer to fetch data about the child from the parent
and switch to querying the child only when the parent is unavailable, or for some reason doesn't have the requested
data (e.g. the connection between parent and the child is broken).
### View streamed metrics in Netdata's dashboard
At this point, the child node is streaming its metrics in real time to its parent. Open the local Agent dashboard for
the parent by navigating to `http://PARENT-NODE:19999` in your browser, replacing `PARENT-NODE` with its IP address or
@ -130,29 +186,7 @@ This dashboard shows parent metrics. To see child metrics, open the left-hand si
in the top panel. Both nodes appear under the **Replicated Nodes** menu. Click on either of the links to switch between
separate parent and child dashboards.
![Switching between parent and child
dashboards](https://user-images.githubusercontent.com/1153921/110043346-761ec000-7d04-11eb-8e58-77670ba39161.gif)
![Switching between parent and child dashboards](https://user-images.githubusercontent.com/1153921/110043346-761ec000-7d04-11eb-8e58-77670ba39161.gif)
The child dashboard is also available directly at `http://PARENT-NODE:19999/host/CHILD-HOSTNAME`, which in this example
is `http://203.0.113.0:19999/host/netdata-child`.
## What's next?
Now that you have a basic streaming setup with replication, you may want to tweak the configuration to eliminate the
child database, disable the child dashboard, or enable SSL on the streaming connection between the parent and child.
See the [streaming reference
doc](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/reference-streaming.md#examples) for details about
other possible configurations.
When using Netdata's default TSDB (`dbengine`), the parent node maintains separate, parallel databases for itself and
every child node streaming to it. Each instance is sized identically based on the `dbengine multihost disk space`
setting in `netdata.conf`. See our doc on [changing metrics retention](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) for
details.
### Related information & further reading
- Streaming
- [How Netdata streams metrics](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md)
- **[Enable streaming between nodes](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md)**
- [Streaming reference](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/reference-streaming.md)

85
docs/metrics-storage-management/how-streaming-works.md
View File

@ -1,85 +0,0 @@
# How metrics streaming works
Each node running Netdata can stream the metrics it collects, in real time, to another node. Streaming allows you to
replicate metrics data across multiple nodes, or centralize all your metrics data into a single time-series database
(TSDB).
When one node streams metrics to another, the node receiving metrics can visualize them on the dashboard, run health checks to
[trigger alarms](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md) and
[send notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md), and
[export](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) all metrics to an external TSDB. When Netdata streams metrics to another
Netdata, the receiving one is able to perform everything a Netdata instance is capable of.
Streaming lets you decide exactly how you want to store and maintain metrics data. While we believe Netdata's
[distributed architecture](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md) is
ideal for speed and scale, streaming provides centralization options and high data availability.
## Streaming basics
There are three types of nodes in Netdata's streaming ecosystem.
- **Parent**: A node, running Netdata, that receives streamed metric data.
- **Child**: A node, running Netdata, that streams metric data to one or more parent.
- **Proxy**: A node, running Netdata, that receives metric data from a child and "forwards" them on to a
separate parent node.
Netdata uses API keys, which are just random GUIDs, to authorize the communication between child and parent nodes. We
recommend using `uuidgen` for generating API keys, which can then be used across any number of streaming connections.
Or, you can generate unique API keys for each parent-child relationship.
Once the parent node authorizes the child's API key, the child can start streaming metrics.
It's important to note that the streaming connection uses TCP, UDP, or Unix sockets, _not HTTP_. To proxy streaming
metrics, you need to use a proxy that tunnels [OSI layer 4-7
traffic](https://en.wikipedia.org/wiki/OSI_model#Layer_4:_Transport_Layer) without interfering with it, such as
[SOCKS](https://en.wikipedia.org/wiki/SOCKS) or Nginx's [TCP/UDP load
balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/).
## Supported streaming configurations
Netdata supports any combination of parent, child, and proxy nodes that you can imagine. Any node can act as both a
parent, child, or proxy at the same time, sending or receiving streaming metrics from any number of other nodes.
Here are a few example streaming configurations:
- **Headless collector**:
- Child `A`, _without_ a database or web dashboard, streams metrics to parent `B`.
- `A` metrics are only available via the local Agent dashboard for `B`.
- `B` generates alarms for `A`.
- **Replication**:
- Child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
- `A` metrics are available on both local Agent dashboards, and can be stored with the same or different metrics
retention policies.
- Both `A` and `B` generate alarms.
- **Proxy**:
- Child `A`, _with or without_ a database, sends metrics to proxy `C`, also _with or without_ a database. `C` sends
metrics to parent `B`.
- Any node with a database can generate alarms.
## Viewing streamed metrics
Parent nodes feature a **Replicated Nodes** section in the left-hand panel, which opens with the hamburger icon
![Hamburger icon](https://raw.githubusercontent.com/netdata/netdata-ui/master/src/components/icon/assets/hamburger.svg)
in the top navigation. The parent node, plus any child nodes, appear here. Click on any of the hostnames to switch
between parent and child dashboards, all served by the parent's [web server](https://github.com/netdata/netdata/blob/master/web/server/README.md).
![Switching between
](https://user-images.githubusercontent.com/1153921/110043346-761ec000-7d04-11eb-8e58-77670ba39161.gif)
Each child dashboard is also available directly at the following URL pattern:
`http://PARENT-NODE:19999/host/CHILD-HOSTNAME`.
## What's next?
Now that you understand the fundamentals of streaming metrics between nodes, go ahead and [enable
streaming](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md) using a simple `parent-child` relationship. For all
the details, see the [streaming reference](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/reference-streaming.md) doc.
Take your streaming setup even further by [exporting metrics](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) to an external TSDB.
### Related information & further reading
- Streaming
- **[How Netdata streams metrics](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md)**
- [Enable streaming between nodes](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md)
- [Streaming reference](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/reference-streaming.md)

2
docs/metrics-storage-management/reference-streaming.md
View File

@ -11,7 +11,7 @@ learn_rel_path: "Configuration"
# Streaming reference
Each node running Netdata can stream the metrics it collects, in real time, to another node. To learn more, read about
[how streaming works](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/how-streaming-works.md).
[how streaming works](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md).
For a quickstart guide for enabling a simple `parent-child` streaming relationship, see our [stream metrics between
nodes](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md) doc. All other configuration options and scenarios are

16
docs/monitor/view-active-alarms.md
View File

@ -1,21 +1,11 @@
<!--
title: "View active health alarms"
description: "View active alarms and their rich data to discover and resolve anomalies and performance issues across your infrastructure."
custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/monitor/view-active-alarms.md"
sidebar_label: "View active health alarms"
learn_status: "Published"
learn_topic_type: "Concepts"
learn_rel_path: "Operations/Alerts"
-->
# View active health alarms
# View active alerts
Every Netdata Agent comes with hundreds of pre-installed health alarms designed to notify you when an anomaly or
performance issue affects your node or the applications it runs.
performance issue affects your node or the applications it runs.
## Netdata Cloud
A War Room's [alarms indicator](https://learn.netdata.cloud/docs/cloud/war-rooms#indicators) displays the number of
A War Room's [indicator](https://learn.netdata.cloud/docs/cloud/war-rooms#indicators) displays the number of
active `critical` (red) and `warning` (yellow) alerts for the nodes in this War Room. Click on either the critical or
warning badges to open a pre-filtered modal displaying only those types of [active
alarms](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/view-active-alerts.md).

6
health/README.md
View File

@ -18,6 +18,6 @@ community-configured alarms for every app/service [the Agent collects metrics fr
silence anything you're not interested in. You can even power complex lookups by running statistical algorithms against
your metrics.
Ready to take the next steps with health monitoring?
[Configuration reference](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md)
You can [use various alert notification methods](https://github.com/netdata/netdata/edit/master/docs/monitor/enable-notifications.md),
[customize alerts](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md), and
[disable/silence](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#disable-or-silence-alerts) alerts.

93
health/REFERENCE.md
View File

@ -37,6 +37,8 @@ You can configure the Agent's health watchdog service by editing files in two lo
Navigate to your [Netdata config directory](https://github.com/netdata/netdata/blob/master/docs/configure/nodes.md) and
use `edit-config` to make changes to any of these files.
### Edit individual alerts
For example, to edit the `cpu.conf` health configuration file, run:
```bash
@ -69,17 +71,53 @@ to the values of your choosing. For example:
crit: $this > (($status == $CRITICAL) ? (75) : (85))
```
Save the file and [reload Netdata's health configuration](#reload-health-configuration) to make your changes live.
Save the file and [reload Netdata's health configuration](#reload-health-configuration) to apply your changes.
### Silence an individual alarm
## Disable or silence alerts
Instead of disabling an alarm altogether, or even disabling _all_ alarms, you can silence individual alarms by changing
one line in a given health entity. To silence any single alarm, change the `to:` line in its entity to `silent`.
Alerts and notifications can be disabled permanently via configuration changes, or temporarily, via the
[health management API](https://github.com/netdata/netdata/blob/master/web/api/health/README.md). The
available options are described below.
### Disable all alerts
In the `netdata.conf` `[health]` section, set `enabled` to `no`, and restart the agent.
### Disable some alerts
In the `netdata.conf` `[health]` section, set `enabled alerms` to a
[simple pattern](https://github.com/netdata/netdata/edit/master/libnetdata/simple_pattern/README.md) that
excludes one or more alerts. e.g. `enabled alarms = !oom_kill *` will load all alarms except `oom_kill`.
You can also [edit the file where the alert is defined](#edit-individual-alerts), comment out its definition,
and [reload Netdata's health configuration](#reload-health-configuration).
### Silence an individual alert
You can stop receiving notification for an individual alert by [changing](#edit-individual-alerts) the `to:` line to `silent`.
```yaml
to: silent
```
This action requires that you [reload Netdata's health configuration](#reload-health-configuration).
### Temporarily disable alerts at runtime
When you need to frequently disable all or some alerts from triggering during certain times (for instance
when running backups) you can use the
[health management API](https://github.com/netdata/netdata/blob/master/web/api/health/README.md).
The API allows you to issue commands to control the health engine's behavior without changing configuration,
or restarting the agent.
### Temporarily silence notifications at runtime
If you want health checks to keep running and alerts to keep getting triggered, but notifications to be
suppressed temporarily, you can use the
[health management API](https://github.com/netdata/netdata/blob/master/web/api/health/README.md).
The API allows you to issue commands to control the health engine's behavior without changing configuration,
or restarting the agent.
## Write a new health entity
While tuning existing alarms may work in some cases, you may need to write entirely new health entities based on how
@ -1124,33 +1162,6 @@ template: ml_5min_node
The `lookup` line will use the `anomaly_rate` dimension of the `anomaly_detection.anomaly_rate` ML chart to calculate the average [node level anomaly rate](https://learn.netdata.cloud/docs/agent/ml#node-anomaly-rate) over the last 5 minues.
## Troubleshooting
You can compile Netdata with [debugging](https://github.com/netdata/netdata/blob/master/daemon/README.md#debugging) and then set in `netdata.conf`:
```yaml
[global]
debug flags = 0x0000000000800000
```
Then check your `/var/log/netdata/debug.log`. It will show you how it works. Important: this will generate a lot of
output in debug.log.
You can find the context of charts by looking up the chart in either `http://NODE:19999/netdata.conf` or
`http://NODE:19999/api/v1/charts`, replacing `NODE` with the IP address or hostname for your Agent dashboard.
You can find how Netdata interpreted the expressions by examining the alarm at
`http://NODE:19999/api/v1/alarms?all`. For each expression, Netdata will return the expression as given in its
config file, and the same expression with additional parentheses added to indicate the evaluation flow of the
expression.
## Disabling health checks or silencing notifications at runtime
It's currently not possible to schedule notifications from within the alarm template. For those scenarios where you need
to temporary disable notifications (for instance when running backups triggers a disk alert) you can disable or silence
notifications are runtime. The health checks can be controlled at runtime via the
[health management API](https://github.com/netdata/netdata/blob/master/web/api/health/README.md).
## Use dimension templates to create dynamic alarms
In v1.18 of Netdata, we introduced **dimension templates** for alarms, which simplifies the process of
@ -1311,3 +1322,23 @@ And how just a few of those dimension template-generated alarms look like in the
All in all, this single entity creates 36 individual alarms. Much easier than writing 36 separate entities in your
health configuration files!
## Troubleshooting
You can compile Netdata with [debugging](https://github.com/netdata/netdata/blob/master/daemon/README.md#debugging) and then set in `netdata.conf`:
```yaml
[global]
debug flags = 0x0000000000800000
```
Then check your `/var/log/netdata/debug.log`. It will show you how it works. Important: this will generate a lot of
output in debug.log.
You can find the context of charts by looking up the chart in either `http://NODE:19999/netdata.conf` or
`http://NODE:19999/api/v1/charts`, replacing `NODE` with the IP address or hostname for your Agent dashboard.
You can find how Netdata interpreted the expressions by examining the alarm at
`http://NODE:19999/api/v1/alarms?all`. For each expression, Netdata will return the expression as given in its
config file, and the same expression with additional parentheses added to indicate the evaluation flow of the
expression.

12
packaging/installer/REINSTALL.md
View File

@ -1,14 +1,4 @@
<!--
title: "Reinstall the Netdata Agent"
description: "Troubleshooting installation issues or force an update of the Netdata Agent by reinstalling it using the same method you used during installation."
custom_edit_url: "https://github.com/netdata/netdata/edit/master/packaging/installer/REINSTALL.md"
sidebar_label: "Reinstall the Netdata Agent"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Installation"
-->
# Reinstall the Netdata Agent
# Reinstall Netdata
In certain situations, such as needing to enable a feature or troubleshoot an issue, you may need to reinstall the
Netdata Agent on your node.

12
packaging/installer/UPDATE.md
View File

@ -1,14 +1,4 @@
<!--
title: "Update the Netdata Agent"
description: "If you opted out of automatic updates, you need to update your Netdata Agent to the latest nightly or stable version."
custom_edit_url: "https://github.com/netdata/netdata/edit/master/packaging/installer/UPDATE.md"
sidebar_label: "Update the Netdata Agent"
learn_status: "Published"
learn_topic_type: "Tasks"
learn_rel_path: "Installation"
-->
# Update the Netdata Agent
# Update Netdata
By default, the Netdata Agent automatically updates with the latest nightly or stable version depending on which
you installed. If you opted out of automatic updates, you need to update your Netdata Agent to the latest nightly

11
packaging/maintainers/README.md
View File

@ -1,13 +1,4 @@
<!--
title: "Package Maintainers"
date: 2020-03-31
custom_edit_url: https://github.com/netdata/netdata/edit/master/packaging/maintainers/README.md
sidebar_label: "Package Maintainers"
learn_status: "Published"
learn_rel_path: "Installation/Package maintainers"
-->
# Package Maintainers
# Package maintainers
This page tracks the package maintainers for Netdata, for various operating systems and versions.

22
streaming/README.md
View File

@ -1,13 +1,4 @@
<!--
title: "Streaming and replication"
description: "Replicate and mirror Netdata's metrics through real-time streaming from child to parent nodes. Then combine, correlate, and export."
custom_edit_url: https://github.com/netdata/netdata/edit/master/streaming/README.md
sidebar_label: "Streaming and replication"
learn_status: "Published"
learn_rel_path: "Configuration"
-->
# Streaming and replication
# Streaming and replication reference
Each Netdata node is able to replicate/mirror its database to another Netdata node, by streaming the collected
metrics in real-time. This is quite different to
@ -22,8 +13,10 @@ When one Netdata node streams metrics another, the receiving instance can use th
- Run health checks that trigger alarms and send alarm notifications
- Export metrics to an external time-series database
This document contains advanced streaming options and suggested deployment options for production.
If you haven't already done so, we suggest you first go through the
[quick introduction to streaming](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md)
, for your first, basic parent child setup.
## Supported configurations
@ -128,10 +121,6 @@ Once the communication is authorized, the sending Netdata node can push metrics
The following sections describe how you can configure sending and receiving Netdata nodes.
##### Options for the sending node
This is the section for the sending Netdata node. On the receiving node, `[stream].enabled` can be `no`.
@ -207,7 +196,6 @@ that use `*` as wildcard (any number of times) and a `!` prefix for a negative m
So: `allow from = !10.1.2.3 10.*` will allow all IPs in `10.*` except `10.1.2.3`. The order is
important: left to right, the first positive or negative match is used.
##### Tracing
When a child is trying to push metrics to a parent or proxy, it logs entries like these: