Remove obsolete or redundant docs (#14476)
Chris Akritidis committed
Feb 8, 2023 at 12:19 UTC
2c899f9f108f0e036cc618d575817744cb6f69f9
9 files changed
-519
docs/Add-more-charts-to-netdata.md
deleted
-17
@@ -1,17 +0,0 @@
1
-<!--
2
-title: "Add more charts to Netdata"
3
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Add-more-charts-to-netdata.md
4
-sidebar_label: "Add more charts to Netdata"
5
-learn_status: "Published"
6
-learn_topic_type: "References"
7
-learn_rel_path: "Possible old, not wanted documents"
8
--->
9
-
10
-# Add more charts to Netdata
11
-
12
-This file has been deprecated. Please see our [collectors docs](https://github.com/netdata/netdata/blob/master/collectors/README.md) for more information.
13
-
14
-## Available data collection modules
15
-
16
-See the [list of supported collectors](https://github.com/netdata/netdata/blob/master/collectors/COLLECTORS.md) to see all the sources Netdata can collect metrics
17
-from.
docs/Donations-netdata-has-received.md
deleted
-33
@@ -1,33 +0,0 @@
1
-<!--
2
-title: "Donations"
3
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/Donations-netdata-has-received.md
4
-sidebar_label: "Donations"
5
-learn_status: "Published"
6
-learn_topic_type: "References"
7
-learn_rel_path: "Possible old, not wanted documents"
8
--->
9
-
10
-# Donations
11
-
12
-This is a list of the donations we have received for Netdata (sorted alphabetically on their name):
13
-
14
-| what donated|related links|who donated|description of the donation|
15
-|-----------:|:-----------:|:---------:|:--------------------------|
16
-| Packages Distribution|-|**[PackageCloud.io](https://packagecloud.io/)**|**PackageCloud.io** donated to a free open-source subscription to their awesome Package Distribution services.|
17
-| Cross Browser Testing|-|**[BrowserStack.com](https://www.browserstack.com/)**|**BrowserStack.com** donated a free subscription to their awesome Browser Testing services (all three of them: Live, Screenshots, Responsive).|
18
-| Cloud VM|[cdn77.my-netdata.io](http://cdn77.my-netdata.io)|**[CDN77.com](https://www.cdn77.com/)**|**CDN77.com** donated a VM with 2 CPU cores, 4GB RAM and 20GB HD, on their excellent CDN network.|
19
-| Localization Management|[Netdata localization project](https://crowdin.com/project/netdata) (check issue [#279](https://github.com/netdata/netdata/issues/279))|**[Crowdin.com](https://crowdin.com/)**|**Crowdin.com** donated an open source license to their Localization Management Platform.|
20
-| Cloud VMs|[london.my-netdata.io](https://london.my-netdata.io) (Several VMs)|**[DigitalOcean.com](https://www.digitalocean.com/)**|**DigitalOcean.com** donated 1000 USD to be used in their excellent Cloud Computing services. Many thanks to [Justin Paine](https://github.com/xxdesmus) for making this happen.|
21
-| Development IDE|-|**[JetBrains.com](https://www.jetbrains.com/)**|**JetBrains.com** donated an open source license for 4 developers for 1 year, to their excellent IDEs.|
22
-| Cloud VM|[octopuscs.my-netdata.io](https://octopuscs.my-netdata.io)|**[OctopusCS.com](https://octopuscs.com/)**|**OctopusCS.com** donated a VM with 4 CPU cores, 16GB RAM and 50GB HD in their excellent Cloud Computing services.|
23
-| Cloud VM|[stackscale.my-netdata.io](https://stackscale.my-netdata.io)|**[stackscale.com](https://www.stackscale.com/)**|**StackScale.com** donated a VM with 4 CPU cores, 16GB RAM and 100GB HD in their excellent Cloud Computing services.|
24
-
25
-Thank you!
26
-
27
----
28
-
29
-**Do you want to donate?** We are thirsty for on-line services that can help us make Netdata better. We also try to build a network of demo sites (VMs) that can help us show the full potential of Netdata.
30
-
31
-Please contact me at costa@tsaousis.gr.
32
-
33
-
docs/README.md
deleted
-21
@@ -1,21 +0,0 @@
1
-<!--
2
-title: "Read documentation on <https://learn.netdata.cloud>"
3
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/README.md
4
-sidebar_label: "Old welcome to Documentation message doc"
5
-learn_status: "Published"
6
-learn_topic_type: "References"
7
-learn_rel_path: "Possible old, not wanted documents"
8
--->
9
-
10
-# Read documentation on <https://learn.netdata.cloud>
11
-
12
-Welcome to the Netdata documentation! While you can read Netdata documentation here, or throughout the Netdata
13
-repository, our intention is that these pages are read on [learn.netdata.cloud](https://learn.netdata.cloud).
14
-
15
-Links between documentation pages will work fine here, but the formatting may not be perfect, as our documentation site
16
-uses a few extra Markdown features that GitHub doesn't support natively. Other things might be missing or look less than
17
-perfect.
18
-
19
-Now get out there and build an exceptional infrastructure.
20
-
21
-
docs/agent-cloud.md
deleted
-82
@@ -1,82 +0,0 @@
1
-<!--
2
-title: "Use the Agent with Netdata Cloud"
3
-date: 2020-05-04
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/agent-cloud.md
5
-sidebar_label: "Use the Agent with Netdata Cloud"
6
-learn_status: "Published"
7
-learn_topic_type: "References"
8
-learn_rel_path: "Possible old, not wanted documents"
9
--->
10
-
11
-# Use the Agent with Netdata Cloud
12
-
13
-While the Netdata Agent is an enormously powerful _distributed_ health monitoring and performance troubleshooting tool,
14
-many of its users need to monitor dozens or hundreds of systems at the same time. That's why we built Netdata Cloud, a
15
-hosted web interface that gives you real-time visibility into your entire infrastructure.
16
-
17
-There are two main ways to use your Agent(s) with Netdata Cloud. You can use both these methods simultaneously, or just
18
-one, based on your needs:
19
-
20
-- Use Netdata Cloud's web interface for monitoring an entire infrastructure, with any number of Agents, in one
21
- centralized dashboard.
22
-- Use **Visited nodes** to quickly navigate between the dashboards of nodes you've recently visited.
23
-
24
-## Monitor an infrastructure with Netdata Cloud
25
-
26
-We designed Netdata Cloud to help you see health and performance metrics, plus active alarms, in a single interface.
27
-Here's what a small infrastructure might look like:
28
-
29
-
30
-
31
-[Read more about Netdata Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx) to better
32
-understand how it gives you real-time
33
-visibility into your entire infrastructure, and why you might consider using it.
34
-
35
-Next, [get started in 5 minutes](https://github.com/netdata/netdata/blob/master/docs/cloud/get-started.mdx), or read our
36
-[connection to Cloud reference](https://github.com/netdata/netdata/blob/master/claim/README.md) for a complete
37
-investigation of Cloud's security and encryption features, plus instructions for Docker containers.
38
-
39
-## Navigate between dashboards with Visited nodes
40
-
41
-If you don't want to use Netdata Cloud's web interface, you can still connect multiple nodes through the **Visited
42
-nodes** menu, which appears on the left-hand side of the dashboard.
43
-
44
-You can use the Visited nodes menu to navigate between the dashboards of many different Agent-monitored systems quickly.
45
-
46
-To add nodes to your Visited nodes menu, you first need to navigate to that node's dashboard, then click the **Sign in**
47
-button at the top of the dashboard. On the screen that appears, which states your node is requesting access to your
48
-Netdata Cloud account, sign in with your preferred method.
49
-
50
-Cloud redirects you back to your node's dashboard, which is now connected to your Netdata Cloud account. You can now see
51
-the Visited nodes menu, which is populated by a single node.
52
-
53
-
54
-
55
-If you previously went through the Cloud onboarding process to create a Space and War Room, you will also see these in
56
-the Visited Nodes menu. You can click on your Space or any of your War Rooms to navigate to Netdata Cloud and continue
57
-monitoring your infrastructure from there.
58
-
59
-
60
-
61
-To add more Agents to your Visited nodes menu, visit them and sign in again. This process connects that node to your
62
-Cloud account and further populates the menu.
63
-
64
-Once you've added more than one node, you can use the menu to switch between various dashboards without remembering IP
65
-addresses or hostnames or saving bookmarks for every node you want to monitor.
66
-
67
-
68
-
69
-## What's next?
70
-
71
-The Agent-Cloud integration is highly adaptable to the needs of any infrastructure or user. If you want to learn more
72
-about how you might want to use or configure Cloud, we recommend the following:
73
-
74
-- Get an overview of Cloud's features by
75
- reading [Cloud documentation](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx).
76
-- Follow the
77
- 5-minute [get started with Cloud](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx)
78
- guide to finish
79
- onboarding and connect your first nodes.
80
-- Better understand how agents connect securely to the Cloud
81
- with [connect agent to Cloud](https://github.com/netdata/netdata/blob/master/claim/README.md) and
82
- [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/aclk/README.md) documentation.
docs/cloud/beta-architecture/new-architecture.md
deleted
-40
@@ -1,40 +0,0 @@
1
-<!--
2
-title: "Test the New Cloud Architecture"
3
-description: "Would you like to be the first to try our new architecture and provide feedback? If so, this guide will help you sign up for our beta testing group."
4
-custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/beta-architecture/new-architecture.md"
5
-sidebar_label: "Test the New Cloud Architecture"
6
-learn_status: "Published"
7
-learn_topic_type: "References"
8
-learn_rel_path: "Possible old, not wanted documents"
9
--->
10
-
11
-To enhance the stability and reliability of Netdata Cloud, we did extensive work on our backend, and we would like to give you the opportunity
12
-to be among the first users to try these changes to our Cloud architecture and provide feedback.
13
-
14
-The backend architecture changes should offer notable improvements in reliability and stability in Netdata Cloud,
15
-but more importantly, it allows us to develop new features and enhanced functionality, including features and enhancements
16
-that you have specifically requested. Features that will be developed on the new architecture include:
17
-
18
-- Parent/Child Cloud relationships
19
-- Alert logs
20
-- Alert management
21
-- Much more
22
-
23
-## Enabling the new architecture
24
-
25
-To enable the new architecture, first ensure that you have installed the latest Netdata version following
26
-[our guide](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx). Then, you or your administrator will need to retrieve the Space IDs
27
-within Netdata Cloud by clicking `Manage Space` in the left pane, selecting the `Space` tab, and copying the value in the `Space Id` field.
28
-You can then send an email to [beta@Netdata.cloud](mailto:beta@netdata.cloud) requesting to be included in our beta testers, and include
29
-in the body of the email a list of Space IDs for any space you would like to have whitelisted for the update. If you received an email
30
-invitation, you can also just reply to the invitation with your Space IDs in the body of the reply.
31
-
32
-Feel free to send the Space IDs for multiple spaces to test the new infrastructure on each of them.
33
-
34
-## Reporting issues
35
-
36
-After you are set up with the new architecture changes, we ask that you report any issues you encounter in our
37
-[designated Discord channel](https://discord.gg/dGzdemHwHh). This feedback
38
-will help us ensure the highest performance of the new architecture and expedite the development and release
39
-of the aforementioned enhancements and features.
40
-
docs/contributing/contributing-documentation.md
deleted
-113
@@ -1,113 +0,0 @@
1
-<!--
2
-title: "Contributing to documentation"
3
-description: "Want to contribute to Netdata's documentation? This guide will set you up with the tools to help others learn about health and performance monitoring."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/contributing/contributing-documentation.md
5
-sidebar_label: "Contributing to documentation"
6
-learn_status: "Published"
7
-learn_topic_type: "References"
8
-learn_rel_path: "Possible old, not wanted documents"
9
--->
10
-
11
-# Contributing to documentation
12
-
13
-We welcome contributions to Netdata's already extensive documentation.
14
-
15
-We store documentation related to the open-source Netdata Agent inside of the [`netdata/netdata`
16
-repository](https://github.com/netdata/netdata) on GitHub. Documentation related to Netdata Cloud is stored in a private
17
-repository and is not currently open to community contributions.
18
-
19
-The Netdata team aggregates and publishes all documentation at [learn.netdata.cloud](https://learn.netdata.cloud/) using
20
-[Docusaurus](https://v2.docusaurus.io/) in a private GitHub repository.
21
-
22
-## Before you get started
23
-
24
-Anyone interested in contributing to documentation should first read the [Netdata style
25
-guide](https://github.com/netdata/netdata/blob/master/docs/contributing/style-guide.md) and the [Netdata Community Code of Conduct](https://github.com/netdata/.github/blob/main/CODE_OF_CONDUCT.md).
26
-
27
-Netdata's documentation uses Markdown syntax. If you're not familiar with Markdown, read the [Mastering
28
-Markdown](https://guides.github.com/features/mastering-markdown/) guide from GitHub for the basics on creating
29
-paragraphs, styled text, lists, tables, and more.
30
-
31
-### Netdata's documentation structure
32
-
33
-Netdata's documentation is separated into four sections.
34
-
35
-- **Netdata**: Documents based on the actions users want to take, and solutions to their problems, such both the Netdata
36
- Agent and Netdata Cloud.
37
- - Stored in various subfolders of the [`/docs` folder](https://github.com/netdata/netdata/tree/master/docs) within the
38
- `netdata/netdata` repository: `/docs/collect`, `/docs/configure`, `/docs/export`, `/docs/get`, `/docs/monitor`,
39
- `/docs/overview`, `/docs/quickstart`, `/docs/store`, and `/docs/visualize`.
40
- - Published at [`https://learn.netdata.cloud/docs`](https://learn.netdata.cloud/docs).
41
-- **Netdata Agent reference**: Reference documentation for the open-source Netdata Agent.
42
- - Stored in various `.md` files within the `netdata/netdata` repository alongside the code responsible for that
43
- feature. For example, the database engine's reference documentation is at `/database/engine/README.md`.
44
- - Published under the **Reference** section in the Netdata Learn sidebar.
45
-- **Netdata Cloud reference**: Reference documentation for the closed-source Netdata Cloud web application.
46
- - Stored in a private GitHub repository and not editable by the community.
47
- - Published at [`https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx`](https://github.com/netdata/netdata/blob/master/docs/cloud/cloud.mdx).
48
-- **Guides**: Solutions-based articles for users who want instructions on completing a specific complex task using the
49
- Netdata Agent and/or Netdata Cloud.
50
- - Stored in the [`/docs/guides` folder](https://github.com/netdata/netdata/tree/master/docs/guides) within the
51
- `netdata/netdata` repository. Organized into subfolders that roughly correlate with the core Netdata documentation.
52
- - Published at [`https://learn.netdata.cloud/guides`](https://learn.netdata.cloud/guides).
53
-
54
-Generally speaking, if you want to contribute to the reference documentation for a specific Netdata Agent feature, find
55
-the appropriate `.md` file co-located with that feature. If you want to contribute documentation that spans features or
56
-products, or has no direct correlation with the existing directory structure, place it in the `/docs` folder within
57
-`netdata/netdata`.
58
-
59
-## How to contribute
60
-
61
-The easiest way to contribute to Netdata's documentation is to edit a file directly on GitHub. This is perfect for small
62
-fixes to a single document, such as fixing a typo or clarifying a confusing sentence.
63
-
64
-Click on the **Edit this page** button on any published document on [Netdata Learn](https://learn.netdata.cloud). Each
65
-page has two of these buttons: One beneath the table of contents, and another at the end of the document, which take you
66
-to GitHub's code editor. Make your suggested changes, keeping [Netdata style guide](https://github.com/netdata/netdata/blob/master/docs/contributing/style-guide.md)
67
-in mind, and use *Preview changes** button to ensure your Markdown syntax works as expected.
68
-
69
-Under the **Commit changes** header, write descriptive title for your requested change. Click the **Commit changes**
70
-button to initiate your pull request (PR).
71
-
72
-Jump down to our instructions on [PRs](#making-a-pull-request) for your next steps.
73
-
74
-### Edit locally
75
-
76
-Editing documentation locally is the preferred method for complex changes that span multiple documents or change the
77
-documentation's style or structure.
78
-
79
-Create a fork of the Netdata Agent repository by visit the [Netdata repository](https://github.com/netdata/netdata) and
80
-clicking on the **Fork** button.
81
-
82
-
84
-
85
-GitHub will ask you where you want to clone the repository. When finished, you end up at the index of your forked
86
-Netdata Agent repository. Clone your fork to your local machine:
87
-
88
-```bash
89
-git clone https://github.com/YOUR-GITHUB-USERNAME/netdata.git
90
-```
91
-
92
-Create a new branch using `git checkout -b BRANCH-NAME`. Use your favorite text editor to make your changes, keeping the
93
-[Netdata style guide](https://github.com/netdata/netdata/blob/master/docs/contributing/style-guide.md) in mind. Add, commit, and push changes to your fork. When
94
-you're finished, visit the [Netdata Agent Pull requests](https://github.com/netdata/netdata/pulls) to create a new pull
95
-request based on the changes you made in the new branch of your fork.
96
-
97
-## Making a pull request
98
-
99
-Pull requests (PRs) should be concise and informative. See our [PR guidelines](https://learn.netdata.cloud/contribute/handbook#pr-guidelines) for
100
-specifics.
101
-
102
-- The title must follow the [imperative mood](https://en.wikipedia.org/wiki/Imperative_mood) and be no more than ~50
103
- characters.
104
-- The description should explain what was changed and why. Verify that you tested any code or processes that you are
105
- trying to change.
106
-
107
-The Netdata team will review your PR and assesses it for correctness, conciseness, and overall quality. We may point to
108
-specific sections and ask for additional information or other fixes.
109
-
110
-After merging your PR, the Netdata team rebuilds the [documentation site](https://learn.netdata.cloud) to publish the
111
-changed documentation.
112
-
113
-
docs/overview/netdata-monitoring-stack.md
deleted
-66
@@ -1,66 +0,0 @@
1
-<!--
2
-title: "Use Netdata standalone or as part of your monitoring stack"
3
-description: "Netdata can run independently or as part of a larger monitoring stack thanks to its flexibility, interoperable core, and exporting features."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/overview/netdata-monitoring-stack.md
5
-sidebar_label: "Use Netdata standalone or as part of your monitoring stack"
6
-learn_status: "Published"
7
-learn_topic_type: "References"
8
-learn_rel_path: "Possible old, not wanted documents"
9
--->
10
-
11
-# Use Netdata standalone or as part of your monitoring stack
12
-
13
-Netdata is an extremely powerful monitoring, visualization, and troubleshooting platform. While you can use it as an
14
-effective standalone tool, we also designed it to be open and interoperable with other tools you might already be using.
15
-
16
-Netdata helps you collect everything and scales to infrastructure of any size, but it doesn't lock-in data or force you
17
-to use specific tools or methodologies. Each feature is extensible and interoperable so they can work in parallel with
18
-other tools. For example, you can use Netdata to collect metrics, visualize metrics with a second open-source program,
19
-and centralize your metrics in a cloud-based time-series database solution for long-term storage or further analysis.
20
-
21
-You can build a new monitoring stack, including Netdata, or integrate Netdata's metrics with your existing monitoring
22
-stack. No matter which route you take, Netdata helps you monitor infrastructure of any size.
23
-
24
-Here are a few ways to enrich your existing monitoring and troubleshooting stack with Netdata:
25
-
26
-## Collect metrics from Prometheus endpoints
27
-
28
-Netdata automatically detects 600 popular endpoints and collects per-second metrics from them via the [generic
29
-Prometheus collector](https://github.com/netdata/go.d.plugin/blob/master/modules/prometheus/README.md). This even
30
-includes support for Windows 10 via [`windows_exporter`](https://github.com/prometheus-community/windows_exporter).
31
-
32
-This collector is installed and enabled on all Agent installations by default, so you don't need to waste time
33
-configuring Netdata. Netdata will detect these Prometheus metrics endpoints and collect even more granular metrics than
34
-your existing solutions. You can now use all of Netdata's meaningfully-visualized charts to diagnose issues and
35
-troubleshoot anomalies.
36
-
37
-## Export metrics to external time-series databases
38
-
39
-Netdata can send its per-second metrics to external time-series databases, such as InfluxDB, Prometheus, Graphite,
40
-TimescaleDB, ElasticSearch, AWS Kinesis Data Streams, Google Cloud Pub/Sub Service, and many others.
41
-
42
-To [export metrics to external time-series databases](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md), you configure an [exporting
43
-_connector_](https://github.com/netdata/netdata/blob/master/docs/export/enable-connector.md). These connectors support filtering and resampling for granular control
44
-over which metrics you export, and at what volume. You can export resampled metrics as collected, as averages, or the
45
-sum of interpolated values based on your needs and other monitoring tools.
46
-
47
-Once you have Netdata's metrics in a secondary time-series database, you can use them however you'd like, such as
48
-additional visualization/dashboarding tools or aggregation of data from multiple sources.
49
-
50
-## Visualize metrics with Grafana
51
-
52
-One popular monitoring stack is Netdata, Graphite, and Grafana. Netdata acts as the stack's metrics collection
53
-powerhouse, Graphite the time-series database, and Grafana the visualization platform. With Netdata at the core, you can
54
-be confident that your monitoring stack is powered by all possible metrics, from all possible sources, from every node
55
-in your infrastructure.
56
-
57
-Of course, just because you export or visualize metrics elsewhere, it doesn't mean Netdata's equivalent features
58
-disappear. You can always build new dashboards in Netdata Cloud, drill down into per-second metrics using Netdata's
59
-charts, or use Netdata's health watchdog to send notifications whenever an anomaly strikes.
60
-
61
-## What's next?
62
-
63
-Whether you're using Netdata standalone or as part of a larger monitoring stack, the next step is the same: [**Get
64
-Netdata**](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx).
65
-
66
-
docs/overview/what-is-netdata.md
deleted
-80
@@ -1,80 +0,0 @@
1
-<!--
2
-title: "What is Netdata?"
3
-description: "Netdata is distributed, real-time performance and health monitoring for systems and applications on a single node or an entire infrastructure."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/overview/what-is-netdata.md
5
-sidebar_label: "What is Netdata"
6
-learn_status: "Published"
7
-learn_topic_type: "Concepts"
8
-learn_rel_path: "Getting started"
9
--->
10
-
11
-# What is Netdata?
12
-
13
-Netdata helps sysadmins, SREs, DevOps engineers, and IT professionals collect all possible metrics from systems and
14
-applications, visualize these metrics in real-time, and troubleshoot complex performance problems.
15
-
16
-Netdata's solution uses two components, the Netdata Agent and Netdata Cloud, to deliver real-time performance and health
17
-monitoring for both single nodes and entire infrastructure.
18
-
19
-## Netdata Agent
20
-
21
-Netdata's distributed monitoring Agent collects thousands of metrics from systems, hardware, and applications with zero
22
-configuration. It runs permanently on all your physical/virtual servers, containers, cloud deployments, and edge/IoT
23
-devices.
24
-
25
-You can [install](https://github.com/netdata/netdata/blob/master/docs/get-started.mdx) Netdata on most Linux
26
-distributions (Ubuntu, Debian, CentOS, and more),
27
-container/microservice platforms (Kubernetes clusters, Docker), and many other operating systems (FreeBSD, macOS), with
28
-no `sudo` required.
29
-
30
-
32
-
33
-## Netdata Cloud
34
-
35
-Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata
36
-Cloud, you can view key metrics, insightful charts, and active alarms from all your nodes in a single web interface.
37
-When an anomaly strikes, seamlessly navigate to any node to troubleshoot and discover the root cause with the familiar
38
-Netdata dashboard.
39
-
40
-**[Netdata Cloud is free](https://www.netdata.cloud/blog/why-netdata-is-free/)**! You can add an entire infrastructure
41
-of nodes, invite all your colleagues, and visualize any number of metrics, charts, and alarms entirely for free.
42
-
43
-While Netdata Cloud offers a centralized method of monitoring your Agents, your metrics data is not stored or
44
-centralized in any way. Metrics data remains with your nodes and is only streamed to your browser, through Cloud, when
45
-you're viewing the Netdata Cloud interface.
46
-
47
-
48
-
49
-## What you can do with Netdata
50
-
51
-Netdata is designed to be both simple to use and flexible for every monitoring, visualization, and troubleshooting use
52
-case:
53
-
54
-- **Collect**: Netdata collects all available metrics from your system and applications with 300+ collectors,
55
- Kubernetes service discovery, and in-depth container monitoring, all while using only 1% CPU and a few MB of RAM. It
56
- even collects metrics from Windows machines.
57
-- **Visualize**: The dashboard meaningfully presents charts to help you understand the relationships between your
58
- hardware, operating system, running apps/services, and the rest of your infrastructure. Add nodes to Netdata Cloud
59
- for a complete view of your infrastructure from a single pane of glass.
60
-- **Monitor**: Netdata's health watchdog uses hundreds of preconfigured alarms to notify you via Slack, email,
61
- PagerDuty and more when an anomaly strikes. Customize with dynamic thresholds, hysteresis, alarm templates, and
62
- role-based notifications.
63
-- **Troubleshoot**: 1s granularity helps you detect and analyze anomalies other monitoring platforms might have
64
- missed. Interactive visualizations reduce your reliance on the console, and historical metrics help you trace issues
65
- back to their root cause.
66
-- **Store**: Netdata's efficient database engine efficiently stores per-second metrics for days, weeks, or even
67
- months. Every distributed node stores metrics locally, simplifying deployment, slashing costs, and enriching
68
- Netdata's interactive dashboards.
69
-- **Export**: Integrate per-second metrics with other time-series databases like Graphite, Prometheus, InfluxDB,
70
- TimescaleDB, and more with Netdata's interoperable and extensible core.
71
-- **Stream**: Aggregate metrics from any number of distributed nodes in one place for in-depth analysis, including
72
- ephemeral nodes in a Kubernetes cluster.
73
-
74
-## What's next?
75
-
76
-Learn more
77
-about [why you should use Netdata](https://github.com/netdata/netdata/blob/master/docs/overview/why-netdata.md),
78
-or [how Netdata works with your existing monitoring stack](https://github.com/netdata/netdata/blob/master/docs/overview/netdata-monitoring-stack.md).
79
-
80
-
docs/overview/why-netdata.md
deleted
-67
@@ -1,67 +0,0 @@
1
-<!--
2
-title: "Why use Netdata?"
3
-description: "Netdata is simple to deploy, scalable, and optimized for troubleshooting. Cut the complexity and expense out of your monitoring stack."
4
-custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/overview/why-netdata.md
5
-sidebar_label: "Why use Netdata"
6
-learn_status: "Published"
7
-learn_topic_type: "Concepts"
8
-learn_rel_path: "Getting started"
9
--->
10
-
11
-# Why use Netdata?
12
-
13
-Netdata takes a different approach to helping people build extraordinary infrastructure. It was built out of frustration
14
-with existing monitoring tools that are too complex, too expensive, and don't help their users actually troubleshoot
15
-complex performance and health issues.
16
-
17
-Netdata is:
18
-
19
-## Simple to deploy
20
-
21
-- **One-line deployment** for Linux distributions, plus support for Kubernetes/Docker infrastructures.
22
-- **Zero configuration and maintenance** required to collect thousands of metrics, every second, from the underlying
23
- OS and running applications.
24
-- **Prebuilt charts and alarms** alert you to common anomalies and performance issues without manual configuration.
25
-- **Distributed storage** to simplify the cost and complexity of storing metrics data from any number of nodes.
26
-
27
-## Powerful and scalable
28
-
29
-- **1% CPU utilization, a few MB of RAM, and minimal disk I/O** to run the monitoring Agent on bare metal, virtual
30
- machines, containers, and even IoT devices.
31
-- **Per-second granularity** for an unlimited number of metrics based on the hardware and applications you're running
32
- on your nodes.
33
-- **Interoperable exporters** let you connect Netdata's per-second metrics with an existing monitoring stack and other
34
- time-series databases.
35
-
36
-## Optimized for troubleshooting
37
-
38
-- **Visual anomaly detection** with a UI/UX that emphasizes the relationships between charts.
39
-- **Customizable dashboards** to pinpoint correlated metrics, respond to incidents, and help you streamline your
40
- workflows.
41
-- **Distributed metrics in a centralized interface** to assist users or teams trace complex issues between distributed
42
- nodes.
43
-
44
-## Comparison with other monitoring solutions
45
-
46
-Netdata offers many benefits over the existing monitoring landscape, whether they're expensive SaaS products or other
47
-open-source tools.
48
-
49
-| Netdata | Others (open-source and commercial) |
50
-| :-------------------------------------------------------------- | :--------------------------------------------------------------- |
51
-| **High resolution metrics** (1s granularity) | Low resolution metrics (10s granularity at best) |
52
-| Collects **thousands of metrics per node** | Collects just a few metrics |
53
-| Fast UI optimized for **anomaly detection** | UI is good for just an abstract view |
54
-| **Long-term, autonomous storage** at one-second granularity | Centralized metrics in an expensive data lake at 10s granularity |
55
-| **Meaningful presentation**, to help you understand the metrics | You have to know the metrics before you start |
56
-| Install and get results **immediately** | Long sales process and complex installation process |
57
-| Use it for **troubleshooting** performance problems | Only gathers _statistics of past performance_ |
58
-| **Kills the console** for tracing performance issues | The console is always required for troubleshooting |
59
-| Requires **zero dedicated resources** | Require large dedicated resources |
60
-
61
-## What's next?
62
-
63
-Whether you already have a monitoring stack you want to integrate Netdata into, or are building something from the
64
-ground-up, you should read more on how Netdata can work either [standalone or as an interoperable part of a monitoring
65
-stack](https://github.com/netdata/netdata/blob/master/docs/overview/netdata-monitoring-stack.md).
66
-
67
-