mirror of
https://github.com/netdata/netdata.git
synced 2025-04-17 11:12:42 +00:00
First batch of adding descriptions to the documentation (#14825)
* first batch of adding descriptions to the documentation, and fixing inconsistencies inside the files * Apply suggestions from code review Co-authored-by: Chris Akritidis <43294513+cakrit@users.noreply.github.com> * Update docs/cloud/visualize/overview.md * Replace view with tab in overview.md --------- Co-authored-by: Chris Akritidis <43294513+cakrit@users.noreply.github.com>
This commit is contained in:
Fotis Voutsas
GitHub
parent
2614786427
commit
5c3084911c
17 changed files with 151 additions and 167 deletions
claim
docs
cloud
dashboard
getting-started
guides/troubleshoot
monitor
quickstart
store
packaging/installer
|
|
@ -1,5 +1,7 @@
|
|||
# Connect Agent to Cloud
|
||||
|
||||
This page will guide you through connecting a Netdata Agent to Netdata Cloud securely, via the encrypted Agent-Cloud link (ACLK).
|
||||
|
||||
You can securely connect a Netdata Agent, running on a distributed node, to Netdata Cloud. A Space's
|
||||
administrator creates a **claiming token**, which is used to add an Agent to their Space via the [Agent-Cloud link
|
||||
(ACLK)](https://github.com/netdata/netdata/blob/master/aclk/README.md).
|
||||
|
|
@ -564,7 +566,7 @@ using the [ACLK](https://github.com/netdata/netdata/blob/master/aclk/README.md).
|
|||
|
||||
| setting | default | info |
|
||||
|:-------------- |:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| cloud base url | https://api.netdata.cloud | The URL for the Netdata Cloud web application. You should not change this. If you want to disable Cloud, change the `enabled` setting. |
|
||||
| cloud base url | <https://api.netdata.cloud> | The URL for the Netdata Cloud web application. You should not change this. If you want to disable Cloud, change the `enabled` setting. |
|
||||
| enabled | yes | The runtime option to disable the [Agent-Cloud link](https://github.com/netdata/netdata/blob/master/aclk/README.md) and prevent your Agent from connecting to Netdata Cloud. |
|
||||
|
||||
### Claiming script
|
||||
|
|
|
|||
|
|
@ -1,5 +1,7 @@
|
|||
# Invite your team
|
||||
|
||||
Invite your entire SRE, DevOPs, or ITOps team to Netdata Cloud, to give everyone insights into your infrastructure from a single pane of glass.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,22 +1,13 @@
|
|||
<!--
|
||||
title: "Netdata Plans"
|
||||
sidebar_label: "Netdata Plans"
|
||||
custom_edit_url: "https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md"
|
||||
sidebar_position: "1000"
|
||||
learn_status: "Published"
|
||||
learn_topic_type: "Concepts"
|
||||
learn_rel_path: "Concepts"
|
||||
learn_docs_purpose: "Explain what are Netdata Plans"
|
||||
-->
|
||||
|
||||
# Netdata Plans
|
||||
|
||||
This page will guide you through the differences between the Community, Pro, Business and Enterprise plans.
|
||||
|
||||
At Netdata, we believe in providing free and unrestricted access to high-quality monitoring solutions, and our commitment to this principle will not change. We offer our free SaaS offering - what we call **Community plan** - and Open Source Agent, which features unlimited nodes and users, unlimited metrics, and retention, providing real-time, high-fidelity, out-of-the-box infrastructure monitoring for packaged applications, containers, and operating systems.
|
||||
|
||||
We also provide paid subscriptions that designed to provide additional features and capabilities for businesses that need tighter and customizable integration of the free monitoring solution to their processes. These are divided into three different plans: **Pro**, **Business**, and **Enterprise**. Each plan will offers a different set of features and capabilities to meet the needs of businesses of different sizes and with different monitoring requirements.
|
||||
|
||||
:::note
|
||||
To not disrupt current users space's access rights we will be keeping their current plan as the **Early Bird** plan. The reason for this is to allow users to
|
||||
To not disrupt current users space's access rights we will be keeping their current plan as the **Early Bird** plan. The reason for this is to allow users to
|
||||
keep using the legacy **Member** role with the exact same permissions as it has currently.
|
||||
|
||||
If you move from the **Early Bird** plan to a paid plan, you will not be able to return to the **Early Bird** plan again. The **Community** free plan will always be available to you, but it does not allow
|
||||
|
|
@ -29,22 +20,26 @@ you to invite or change users using the Member role. See more details on our [ro
|
|||
The plan is an attribute that is directly attached to your space(s) and that dictates what capabilities and customizations you have on your space. If you have different spaces you can have different Netdata plans on them. This gives you flexibility to chose what is more adequate for your needs on each of your spaces.
|
||||
|
||||
Netdata Cloud plans, with the exception of Community, work as subscriptions and overall consist of two pricing components:
|
||||
|
||||
* A flat fee component, that is a price per space, and
|
||||
* An on-demand metered component, that is related to your usage of Netdata which directly links to the [number of nodes you have running](#running-nodes-and-billing)
|
||||
|
||||
Netdata provides two billing frequency options:
|
||||
|
||||
* Monthly - Pay as you go, where we charge both the flat fee and the on-demand component every month
|
||||
* Yearly - Annual prepayment, where we charge upfront the flat fee and committed amount related to your estimated usage of Netdata (more details [here](#committed-nodes))
|
||||
|
||||
For more details on the plans and subscription conditions please check https://netdata.cloud/pricing.
|
||||
For more details on the plans and subscription conditions please check <https://netdata.cloud/pricing>.
|
||||
|
||||
#### Running nodes and billing
|
||||
|
||||
The only dynamic variable we consider for billing is the number of concurrently running nodes or agents. We only charge you for your active running nodes, so we don't count:
|
||||
|
||||
* offline nodes
|
||||
* stale nodes, nodes that are available to query through a Netdata parent agent but are not actively connecting metrics at the moment
|
||||
|
||||
To ensure we don't overcharge you due to sporadic spikes throughout a month or even at a certain point in a day we are:
|
||||
|
||||
* Calculate a daily P90 figure for your running nodes. To achieve that, we take a daily snapshot of your running nodes, and using the node state change events (live, offline) we guarantee that a daily P90 figure is calculated to remove any daily spikes
|
||||
* On top of the above, we do a running P90 calculation from the start to the end of your billing cycle. Even if you have an yearly billing frequency we keep a monthly subscription linked to that to identify any potential overage over your [committed nodes](#committed-nodes).
|
||||
|
||||
|
|
@ -63,13 +58,14 @@ If, for a given month, your usage is over these committed nodes we will charge t
|
|||
It is ok to change your mind. We allow to change your plan, billing frequency or adjust the committed nodes, on yearly plans, at any time.
|
||||
|
||||
To achieve this you will need to:
|
||||
|
||||
* Move to the Community plan, where we will cancel the current subscription and:
|
||||
* Issue a credit to you for the unused period, in case you are on a **yearly plan**
|
||||
* Charge you only for the current used period and issue a credit for the unused period related to the flat fee, in case you are on a **monthly plan**
|
||||
* Issue a credit to you for the unused period, in case you are on a **yearly plan**
|
||||
* Charge you only for the current used period and issue a credit for the unused period related to the flat fee, in case you are on a **monthly plan**
|
||||
* Select the new subscription with the change that you want
|
||||
|
||||
> ⚠️ On a move to Community (cancellation of an active subscription), please note that you will have all your notification methods configurations active **for a period of 24 hours**.
|
||||
> After that, any notification methods unavailable in your new plan at that time will be automatically disabled. You can always re-enable them once you move to a paid plan that includes them.
|
||||
> After that, any notification methods unavailable in your new plan at that time will be automatically disabled. You can always re-enable them once you move to a paid plan that includes them.
|
||||
|
||||
> ⚠️ Any credit given to you will be available to use on future paid subscriptions with us. It will be available until the the **end of the following year**.
|
||||
|
||||
|
|
@ -86,7 +82,7 @@ Depending on the plan associated to your space you will have different roles ava
|
|||
| **Troubleshooters**<p>Users with this role can use Netdata to troubleshoot, not manage entities.</p><p>They can access any War Room in the Space.</p> | - | :heavy_check_mark: | :heavy_check_mark: | - |
|
||||
| **Observers**<p>Users with this role can only view data in specific War Rooms.</p>💡 Ideal for restricting your customer's access to their own dedicated rooms.<p></p> | - | - | :heavy_check_mark: | - |
|
||||
| **Billing**<p>Users with this role can handle billing options and invoices.</p> | - | - | :heavy_check_mark: | - |
|
||||
| **Member** ⚠️ Legacy role<p>Users with this role can create War Rooms and invite other Members.</p><p>They can only see the War Rooms they belong to and all Nodes in the All Nodes room.</p>| - | - | - | :heavy_check_mark: |
|
||||
| **Member** ⚠️ Legacy role<p>Users with this role can create War Rooms and invite other Members.</p><p>They can only see the War Rooms they belong to and all Nodes in the All Nodes room.</p>| - | - | - | :heavy_check_mark: |
|
||||
|
||||
For more details check the documentation under [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md).
|
||||
|
||||
|
|
@ -105,6 +101,7 @@ For more details check the documentation under [Events feed](https://github.com/
|
|||
##### Notification integrations
|
||||
|
||||
The plan on your space will determine what type of notifications methods will be available to you:
|
||||
|
||||
* **Community** - Email and Discord
|
||||
* **Pro** - Email, Discord and webhook
|
||||
* **Business** - Unlimited, this includes Slack, PagerDuty, etc.
|
||||
|
|
@ -114,11 +111,12 @@ For mode details check the documentation under [Alert Notifications](https://git
|
|||
### Related Topics
|
||||
|
||||
#### **Related Concepts**
|
||||
- [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)
|
||||
- [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
|
||||
- [Events feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md)
|
||||
- [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)
|
||||
|
||||
* [Spaces](https://github.com/netdata/netdata/blob/master/docs/cloud/spaces.md)
|
||||
* [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md)
|
||||
* [Events feed](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/events-feed.md)
|
||||
* [Role-Based Access model](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/role-based-access.md)
|
||||
|
||||
#### Related Tasks
|
||||
- [View Plan & Billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md)
|
||||
|
||||
* [View Plan & Billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Sign in with email, Google, or GitHub
|
||||
# Sign in to Netdata
|
||||
|
||||
This page explains how to sign in to Netdata with your email, Google account, or GitHub account, and provides some tips if you're having trouble signing in.
|
||||
|
||||
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
|
||||
|
|
@ -7,7 +9,6 @@ with a Netdata Cloud account.
|
|||
No matter the method, your Netdata Cloud account is based around your email address. Netdata Cloud does not store
|
||||
passwords.
|
||||
|
||||
|
||||
## Email
|
||||
|
||||
To sign in with email, visit [Netdata Cloud](https://app.netdata.cloud/sign-in?cloudRoute=spaces?utm_source=docs&utm_content=sign_in_button_email_section), enter your email address, and click
|
||||
|
|
@ -31,22 +32,22 @@ quickstart](https://github.com/netdata/netdata/blob/master/packaging/installer/R
|
|||
|
||||
### Troubleshooting
|
||||
|
||||
You should receive your sign in email in less than a minute. The subject is **Verify your email!** for new sign-ups, **Sign in to Netdata** for sign ins.
|
||||
You should receive your sign in email in less than a minute. The subject is **Verify your email!** for new sign-ups, **Sign in to Netdata** for sign ins.
|
||||
The sender is `no-reply@netdata.cloud` via `sendgrid.net`.
|
||||
|
||||
If you don't see the email, try the following:
|
||||
|
||||
- Check your spam folder.
|
||||
- In Gmail, check the **Updates** category.
|
||||
- Check [Netdata Cloud status](https://status.netdata.cloud) for ongoing issues with our infrastructure.
|
||||
- Request another sign in email via the [sign in page](https://app.netdata.cloud/sign-in?cloudRoute=spaces?utm_source=docs&utm_content=sign_in_button_troubleshooting_section).
|
||||
- Check your spam folder.
|
||||
- In Gmail, check the **Updates** category.
|
||||
- Check [Netdata Cloud status](https://status.netdata.cloud) for ongoing issues with our infrastructure.
|
||||
- Request another sign in email via the [sign in page](https://app.netdata.cloud/sign-in?cloudRoute=spaces?utm_source=docs&utm_content=sign_in_button_troubleshooting_section).
|
||||
|
||||
You may also want to add `no-reply@netdata.cloud` to your address book or contacts list, especially if you're using
|
||||
a public email service, such as Gmail. You may also want to whitelist/allowlist either the specific email or the entire
|
||||
`netdata.cloud` domain.
|
||||
|
||||
In some cases, temporary issues with your mail server or email account may result in your email address being added to a Bounce list by Sendgrid.
|
||||
If you are added to that list, no Netdata cloud email can reach you, including alarm notifications. Let us know in Discord that you have trouble receiving
|
||||
If you are added to that list, no Netdata cloud email can reach you, including alarm notifications. Let us know in Discord that you have trouble receiving
|
||||
any email from us and someone will ask you to provide your email address privately, so we can check if you are on the Bounce list.
|
||||
|
||||
## Google and GitHub OAuth
|
||||
|
|
@ -56,7 +57,7 @@ receives via OAuth.
|
|||
|
||||
To sign in with Google or GitHub OAuth, visit [Netdata Cloud](https://app.netdata.cloud/sign-in?cloudRoute=spaces?utm_source=docs&utm_content=sign_in_button_google_github_section) and click the
|
||||
**Continue with Google/GitHub** or button. Enter your Google/GitHub username and your password. Complete two-factor
|
||||
authentication if you or your organization has it enabled.
|
||||
authentication if you or your organization has it enabled.
|
||||
|
||||
You are then signed in to Netdata Cloud or directed to the new-user onboarding if you have not signed up previously.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,79 +1,81 @@
|
|||
# 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.
|
||||
|
||||
#### Prerequisites
|
||||
## Prerequisites
|
||||
|
||||
To see your plan and billing setting you need:
|
||||
|
||||
- A Cloud account
|
||||
- Access to the space as an Administrator or Billing user
|
||||
|
||||
#### Steps
|
||||
## Steps
|
||||
|
||||
1. Click on the **Space settings** cog (located above your profile icon)
|
||||
1. Click on the **Plan & Billing** tab
|
||||
1. On this page you will be presented with information on your current plan, billing settings, and usage information:
|
||||
1. At the top of the page you will see:
|
||||
* **Credit** amount which refers to any amount you have available to use on future invoices or subscription changes (https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance) - this is displayed once you have had an active paid subscription with us
|
||||
* **Billing email** the email that was specified to be linked to tha plan subscription. This is where invoices, payment, and subscription-related notifications will be sent.
|
||||
* **Billing options and Invoices** is the link to our billing provider Customer Portal where you will be able to:
|
||||
* See the current subscription. There will always be 2 subscriptions active for the two pricing components mentioned on [Netdata Plans documentation page](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plans)
|
||||
* Change directly the payment method associated to current subscriptions
|
||||
* View, add, delete or change your default payment methods
|
||||
* View or change or Billing information:
|
||||
* Billing email
|
||||
* Address
|
||||
* Phone number
|
||||
* Tax ID
|
||||
* View your invoice history
|
||||
- **Credit** amount which refers to any amount you have available to use on future invoices or subscription changes (<https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plan-changes-and-credit-balance>) - this is displayed once you have had an active paid subscription with us
|
||||
- **Billing email** the email that was specified to be linked to tha plan subscription. This is where invoices, payment, and subscription-related notifications will be sent.
|
||||
- **Billing options and Invoices** is the link to our billing provider Customer Portal where you will be able to:
|
||||
- See the current subscription. There will always be 2 subscriptions active for the two pricing components mentioned on [Netdata Plans documentation page](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plans)
|
||||
- Change directly the payment method associated to current subscriptions
|
||||
- View, add, delete or change your default payment methods
|
||||
- View or change or Billing information:
|
||||
- Billing email
|
||||
- Address
|
||||
- Phone number
|
||||
- Tax ID
|
||||
- View your invoice history
|
||||
1. At the middle, you'll see details on your current plan as well as means to:
|
||||
* Upgrade or cancel your plan
|
||||
* View full plan details page
|
||||
- Upgrade or cancel your plan
|
||||
- View full plan details page
|
||||
1. At the bottom, you will find your Usage chart that displays:
|
||||
* Daily count - The weighted 90th percentile of the live node count during the day, taking time as the weight. If you have 30 live nodes throughout the day
|
||||
- Daily count - The weighted 90th percentile of the live node count during the day, taking time as the weight. If you have 30 live nodes throughout the day
|
||||
except for a two hour peak of 44 live nodes, the daily value is 31.
|
||||
* Period count: The 90th percentile of the daily counts for this period up to the date. The last value for the period is used as the number of nodes for the bill for that period. See more details in [running nodes and billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#running-nodes-and-billing) (only applicable if you are on a paid plan subscription)
|
||||
* Committed nodes: The number of nodes committed to in the yearly plan. In case the period count is higher than the number of committed nodes, the difference is billed as overage.
|
||||
- Period count: The 90th percentile of the daily counts for this period up to the date. The last value for the period is used as the number of nodes for the bill for that period. See more details in [running nodes and billing](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#running-nodes-and-billing) (only applicable if you are on a paid plan subscription)
|
||||
- Committed nodes: The number of nodes committed to in the yearly plan. In case the period count is higher than the number of committed nodes, the difference is billed as overage.
|
||||
|
||||
> ⚠️ At the moment, any changes to an active paid plan, upgrades, change billing frequency or committed nodes, will be a manual two-setup flow:
|
||||
>
|
||||
> 1. cancel your current subscription - move you to the Community plan
|
||||
> 2. chose the plan with the intended changes
|
||||
>
|
||||
> This is a temporary process that we aim to sort out soon so that it will effortless for you to do any of these actions.
|
||||
|
||||
### FAQ
|
||||
## FAQ
|
||||
|
||||
#### 1. What Payment Methods are accepted?
|
||||
### 1. What Payment Methods are accepted?
|
||||
|
||||
You can easily pay online via most major Credit/Debit Cards. More payment options are expected to become available in the near future.
|
||||
You can easily pay online via most major Credit/Debit Cards. More payment options are expected to become available in the near future.
|
||||
|
||||
#### 2. What happens if a renewal payment fails?
|
||||
### 2. What happens if a renewal payment fails?
|
||||
|
||||
After an initial failed payment, we will attempt to process your payment every week for the next 15 days. After three failed attempts your Space will be moved to the **Community** plan (free forever).
|
||||
After an initial failed payment, we will attempt to process your payment every week for the next 15 days. After three failed attempts your Space will be moved to the **Community** plan (free forever).
|
||||
|
||||
For the next 24 hours, you will be able to use all your current notification method configurations. After 24 hours, any of the notification method configurations that aren't available on your space's plan will be automatically disabled.
|
||||
|
||||
Cancellation might affect users in your Space. Please check what roles are available on the [Community plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#areas-impacted-by-plans). Users with unavailable roles on the Community plan will immediately have restricted access to the Space.
|
||||
|
||||
#### 3. Which currencies do you support?
|
||||
### 3. Which currencies do you support?
|
||||
|
||||
We currently accept payments only in US Dollars (USD). We currently have plans to also accept payments in Euros (EUR), but do not currently have an estimate for when such support will be available.
|
||||
|
||||
#### 4. Can I get a refund? How?
|
||||
### 4. Can I get a refund? How?
|
||||
|
||||
Payments for Netdata subscriptions are refundable **only** if you cancel your subscription within 14 days of purchase. The refund will be credited to the Credit/Debit Card used for making the purchase. To request a refund, please email us at [billing@netdata.cloud](mailto:billing@netdata.cloud).
|
||||
|
||||
#### 5. How do I cancel my paid Plan?
|
||||
|
||||
Your annual or monthly Netdata Subscription plan will automatically renew until you cancel it. You can cancel your paid plan at any time by clicking ‘Cancel Plan’ from the **Plan & Billing** section under settings. You can also cancel your paid Plan by clicking the _Select_ button under **Community** plan in the **Plan & Billing** Section under Settings.
|
||||
### 5. How do I cancel my paid Plan?
|
||||
|
||||
#### 6. How can I access my Invoices/Receipts after I paid for a Plan?
|
||||
Your annual or monthly Netdata Subscription plan will automatically renew until you cancel it. You can cancel your paid plan at any time by clicking ‘Cancel Plan’ from the **Plan & Billing** section under settings. You can also cancel your paid Plan by clicking the _Select_ button under **Community** plan in the **Plan & Billing** Section under Settings.
|
||||
|
||||
### 6. How can I access my Invoices/Receipts after I paid for a Plan?
|
||||
|
||||
You can visit the _Billing Options & Invoices_ in the **Plan & Billing** section under settings in your Netdata Space where you can find all your Invoicing history.
|
||||
|
||||
#### 7. Why do I see two separate Invoices?
|
||||
### 7. Why do I see two separate Invoices?
|
||||
|
||||
Every time you purchase or renew a Plan, two separate Invoices are generated:
|
||||
|
||||
|
|
@ -81,15 +83,10 @@ Every time you purchase or renew a Plan, two separate Invoices are generated:
|
|||
|
||||
- The other Invoice includes your monthly “On Demand - Usage”.
|
||||
|
||||
Right after the activation of your subscription, you will receive a zero value Invoice since you had no usage when you subscribed.
|
||||
Right after the activation of your subscription, you will receive a zero value Invoice since you had no usage when you subscribed.
|
||||
|
||||
On the following month you will receive an Invoice based on your monthly usage.
|
||||
|
||||
You can find some further details on the [Netdata Plans page](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#plans).
|
||||
|
||||
> ⚠️ We expect this to change to a single invoice in the future, but currently do not have a concrete timeline for when this change will happen.
|
||||
|
||||
|
||||
#### Related topics
|
||||
|
||||
- [Netdata Plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Spaces
|
||||
# Netdata Cloud Spaces
|
||||
|
||||
Organize your multi-organization infrastructure monitoring on Netdata Cloud by creating Spaces to completely isolate access to your Agent-monitored nodes.
|
||||
|
||||
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.
|
||||
|
|
@ -74,8 +76,3 @@ Netdata admin users now have the ability to remove obsolete nodes from a space.
|
|||
- If the obsoleted nodes eventually become live or online once more they will be automatically re-added to the space
|
||||
|
||||
|
||||
|
||||
## What's next?
|
||||
|
||||
Once you configured your Spaces, it's time to set up
|
||||
your [War Rooms](https://github.com/netdata/netdata/blob/master/docs/cloud/war-rooms.md).
|
||||
|
|
|
|||
|
|
@ -1,5 +1,7 @@
|
|||
# Interact with charts
|
||||
|
||||
Learn how to use Netdata's powerful charts to troubleshoot with real-time, per-second metric data.
|
||||
|
||||
Netdata excels in collecting, storing, and organizing metrics in out-of-the-box dashboards.
|
||||
To make sense of all the metrics, Netdata offers an enhanced version of charts that update every second.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +1,12 @@
|
|||
# Node filter
|
||||
|
||||
The node filter allows you to quickly filter the nodes visualized in a War Room's views.
|
||||
It appears on all views, except on single-node dashboards.
|
||||
The node filter allows you to quickly filter the nodes visualized in a War Room's views. It appears on all views, except on single-node dashboards.
|
||||
|
||||
Inside the filter, the nodes get categorized into three groups:
|
||||
|
||||
- Live nodes
|
||||
Nodes that are currently online, collecting and streaming metrics to Cloud.
|
||||
- Live nodes display
|
||||
raised [Alert](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md) counters,
|
||||
[Machine Learning](https://github.com/netdata/netdata/blob/master/ml/README.md) availability,
|
||||
and [Functions](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-functions.md) availability
|
||||
- Live nodes display raised [Alert](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alarms.md) counters, [Machine Learning](https://github.com/netdata/netdata/blob/master/ml/README.md) availability, and [Functions](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-functions.md) availability
|
||||
- Stale nodes
|
||||
Nodes that are offline and not streaming metrics to Cloud. Only historical data can be presented from a parent node.
|
||||
- For these nodes you can only see their ML status, as they are not online to provide more information
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Home, overview and single node views
|
||||
# Home, overview and single node tabs
|
||||
|
||||
Learn how to use the Home, Overview, and Single Node tabs in Netdata Cloud, to explore your infrastructure and troubleshoot issues.
|
||||
|
||||
## Home
|
||||
|
||||
|
|
@ -7,7 +9,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 tab
|
||||
|
||||
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**.
|
||||
|
|
@ -16,8 +18,7 @@ These charts display real-time aggregated metrics from all the nodes (or a filte
|
|||
When you [interact with composite charts](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md)
|
||||
you can see your infrastructure from a single pane of glass, discover trends or anomalies, and perform root cause analysis.
|
||||
|
||||
The Single Node view dashboard is exactly the same as the Overview, but with a hard-coded filter to only show
|
||||
a single node.
|
||||
The Single Node tab dashboard is exactly the same as the Overview, but with a hard-coded filter to only show a single node.
|
||||
|
||||
### Chart navigation Menu
|
||||
|
||||
|
|
@ -30,25 +31,18 @@ monitor an Apache web server, the **Apache** section still appears and displays
|
|||
One difference between the Netdata Cloud menu and those found in local Agent dashboards is that
|
||||
the Overview condenses multiple services, families, or instances into single sections, sub-menus, and associated charts.
|
||||
|
||||
For services, let's say you have two concurrent jobs with the
|
||||
[web_log collector](https://github.com/netdata/go.d.plugin/blob/master/modules/weblog/README.md), one for Apache and
|
||||
another for Nginx. A single-node or
|
||||
local dashboard shows two section, **web_log apache** and **web_log nginx**, whereas the Overview condenses these into a
|
||||
For services, let's say you have two concurrent jobs with the [web_log collector](https://github.com/netdata/go.d.plugin/blob/master/modules/weblog/README.md), one for Apache and another for Nginx.
|
||||
A single-node or local dashboard shows two section, **web_log apache** and **web_log nginx**, whereas the Overview condenses these into a
|
||||
single **web_log** section containing composite charts from both jobs.
|
||||
|
||||
The Cloud also condenses multiple families or multiple instances into a single **all** sub-menu and associated
|
||||
charts. For example, if Node A has 5 disks, and Node B has 3, each disk contributes to a single `disk.io` composite
|
||||
chart. The utility bar should show that there are 8 charts from 2 nodes contributing to that chart. The aggregation applies
|
||||
to disks, network devices, and other metric types that involve multiple instances of a piece of hardware or software.
|
||||
The Cloud also condenses multiple families or multiple instances into a single **all** sub-menu and associated charts.
|
||||
For example, if Node A has 5 disks, and Node B has 3, each disk contributes to a single `disk.io` composite chart.
|
||||
The utility bar should show that there are 8 charts from 2 nodes contributing to that chart.
|
||||
The aggregation applies to disks, network devices, and other metric types that involve multiple instances of a piece of hardware or software.
|
||||
|
||||
## Persistence of composite chart settings
|
||||
|
||||
Of course you can
|
||||
[change the filtering or grouping](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md)
|
||||
of metrics in the composite charts that aggregate all these instances, to see only the information you are interested in,
|
||||
and save that view in a custom dashboard.
|
||||
|
||||
When you change a composite chart via its definition bar, Netdata Cloud persists these settings in a query string
|
||||
attached to the URL in your browser. You can "save" these settings by bookmarking this particular URL, or share it with
|
||||
colleagues by having them copy-paste it into their browser.
|
||||
Of course you can [change the filtering or grouping](https://github.com/netdata/netdata/blob/master/docs/cloud/visualize/interact-new-charts.md) of metrics in the composite charts that aggregate all these instances, to see only the information you are interested in, and save that tab in a custom dashboard.
|
||||
|
||||
When you change a composite chart via its definition bar, Netdata Cloud persists these settings in a query string attached to the URL in your browser.
|
||||
You can "save" these settings by bookmarking this particular URL, or share it with colleagues by having them copy-paste it into their browser.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,6 @@
|
|||
# War rooms
|
||||
# Netdata Cloud War rooms
|
||||
|
||||
War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and
|
||||
visualizations.
|
||||
Netdata Cloud uses War Rooms to organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
|
||||
|
||||
Once you add nodes to a Space, all of your nodes will be visible in the **All nodes** War Room. This is a special War Room
|
||||
which gives you an overview of all of your nodes in this particular Space. Then you can create functional separations of
|
||||
|
|
|
|||
|
|
@ -1,5 +1,9 @@
|
|||
# Visualization date and time controls
|
||||
|
||||
Netdata's dashboard features powerful date visualization controls that include a time control, a timezone selector and a rich date and timeframe selector.
|
||||
|
||||
The controls come with useful defaults and rich customization, to help you narrow your focus when troubleshooting issues or anomalies.
|
||||
|
||||
## Time controls
|
||||
|
||||
The time control provides you the following options: **Play**, **Pause** and **Force Play**.
|
||||
|
|
@ -17,7 +21,6 @@ Main use cases for **Force Play**:
|
|||
|
||||
|
||||
|
||||
|
||||
## Date and time selector
|
||||
|
||||
The date and time selector allows you to change the visible timeframe and change the timezone used in the interface.
|
||||
|
|
@ -78,7 +81,6 @@ beyond stored historical metrics, you'll see this message:
|
|||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,6 @@
|
|||
# Getting started
|
||||
# Getting started with Netdata
|
||||
|
||||
Learn how Netdata can get you monitoring your infrastructure in minutes.
|
||||
|
||||
## What is Netdata ?
|
||||
|
||||
|
|
@ -12,34 +14,34 @@ Netdata is:
|
|||
|
||||
### Simple to deploy
|
||||
|
||||
- **One-line deployment** for Linux distributions, plus support for Kubernetes/Docker infrastructures.
|
||||
- **Zero configuration and maintenance** required to collect thousands of metrics, every second, from the underlying
|
||||
- **One-line deployment** for Linux distributions, plus support for Kubernetes/Docker infrastructures.
|
||||
- **Zero configuration and maintenance** required to collect thousands of metrics, every second, from the underlying
|
||||
OS and running applications.
|
||||
- **Prebuilt charts and alarms** alert you to common anomalies and performance issues without manual configuration.
|
||||
- **Distributed storage** to simplify the cost and complexity of storing metrics data from any number of nodes.
|
||||
- **Prebuilt charts and alarms** alert you to common anomalies and performance issues without manual configuration.
|
||||
- **Distributed storage** to simplify the cost and complexity of storing metrics data from any number of nodes.
|
||||
|
||||
### Powerful and scalable
|
||||
|
||||
- **1% CPU utilization, a few MB of RAM, and minimal disk I/O** to run the monitoring Agent on bare metal, virtual
|
||||
- **1% CPU utilization, a few MB of RAM, and minimal disk I/O** to run the monitoring Agent on bare metal, virtual
|
||||
machines, containers, and even IoT devices.
|
||||
- **Per-second granularity** for an unlimited number of metrics based on the hardware and applications you're running
|
||||
- **Per-second granularity** for an unlimited number of metrics based on the hardware and applications you're running
|
||||
on your nodes.
|
||||
- **Interoperable exporters** let you connect Netdata's per-second metrics with an existing monitoring stack and other
|
||||
- **Interoperable exporters** let you connect Netdata's per-second metrics with an existing monitoring stack and other
|
||||
time-series databases.
|
||||
|
||||
### Optimized for troubleshooting
|
||||
|
||||
- **Visual anomaly detection** with a UI/UX that emphasizes the relationships between charts.
|
||||
- **Customizable dashboards** to pinpoint correlated metrics, respond to incidents, and help you streamline your
|
||||
- **Visual anomaly detection** with a UI/UX that emphasizes the relationships between charts.
|
||||
- **Customizable dashboards** to pinpoint correlated metrics, respond to incidents, and help you streamline your
|
||||
workflows.
|
||||
- **Distributed metrics in a centralized interface** to assist users or teams trace complex issues between distributed
|
||||
- **Distributed metrics in a centralized interface** to assist users or teams trace complex issues between distributed
|
||||
nodes.
|
||||
|
||||
### Secure by design
|
||||
|
||||
- **Distributed data architecture** so fast and efficient, there’s no limit to the number of metrics you can follow.
|
||||
- Because your data is **stored at the edge**, security is ensured.
|
||||
-
|
||||
- **Distributed data architecture** so fast and efficient, there’s no limit to the number of metrics you can follow.
|
||||
- Because your data is **stored at the edge**, security is ensured.
|
||||
|
||||
### Comparison with other monitoring solutions
|
||||
|
||||
Netdata offers many benefits over the existing monitoring landscape, whether they're expensive SaaS products or other
|
||||
|
|
@ -57,21 +59,19 @@ open-source tools.
|
|||
| **Kills the console** for tracing performance issues | The console is always required for troubleshooting |
|
||||
| Requires **zero dedicated resources** | Require large dedicated resources |
|
||||
|
||||
|
||||
Netdata works with tons of applications, notifications platforms, and other time-series databases:
|
||||
|
||||
- **300+ system, container, and application endpoints**: Collectors autodetect metrics from default endpoints and
|
||||
- **300+ system, container, and application endpoints**: Collectors autodetect metrics from default endpoints and
|
||||
immediately visualize them into meaningful charts designed for troubleshooting. See [everything we
|
||||
support](https://github.com/netdata/netdata/blob/master/collectors/COLLECTORS.md).
|
||||
- **20+ notification platforms**: Netdata's health watchdog sends warning and critical alarms to your [favorite
|
||||
- **20+ notification platforms**: Netdata's health watchdog sends warning and critical alarms to your [favorite
|
||||
platform](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md) to inform you of anomalies just seconds
|
||||
after they affect your node.
|
||||
- **30+ external time-series databases**: Export resampled metrics as they're collected to other [local- and
|
||||
- **30+ external time-series databases**: Export resampled metrics as they're collected to other [local- and
|
||||
Cloud-based databases](https://github.com/netdata/netdata/blob/master/docs/export/external-databases.md) for best-in-class
|
||||
interoperability.
|
||||
|
||||
|
||||
## How it works
|
||||
## How it works
|
||||
|
||||
Netdata is a highly efficient, highly modular, metrics management engine. Its lockless design makes it ideal for concurrent operations on the metrics.
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ And a higher level diagram in this one.
|
|||
|
||||
|
||||
You can even visit this slightly dated [interactive infographic](https://my-netdata.io/infographic.html) and get lost in a rabbit hole.
|
||||
You can even visit this slightly dated [interactive infographic](https://my-netdata.io/infographic.html) and get lost in a rabbit hole.
|
||||
|
||||
But the best way to get under the hood or in the steering wheel of our highly efficient, low-latency system (supporting multiple readers and one writer on each metric) is to read the rest of our docs, or just to jump in and [get started](https://github.com/netdata/netdata/blob/master/packaging/installer/README.md). But here's a good breakdown:
|
||||
|
||||
|
|
@ -95,6 +95,7 @@ Netdata's distributed monitoring Agent collects thousands of metrics from system
|
|||
You can install Netdata on most Linux distributions (Ubuntu, Debian, CentOS, and more), container/microservice platforms (Kubernetes clusters, Docker), and many other operating systems (FreeBSD, macOS), with no sudo required.
|
||||
|
||||
### Netdata Cloud
|
||||
|
||||
Netdata Cloud is a web application that gives you real-time visibility for your entire infrastructure. With Netdata Cloud, you can view key metrics, insightful charts, and active alarms from all your nodes in a single web interface. When an anomaly strikes, seamlessly navigate to any node to troubleshoot and discover the root cause with the familiar Netdata dashboard.
|
||||
|
||||
Netdata Cloud is free! You can add an entire infrastructure of nodes, invite all your colleagues, and visualize any number of metrics, charts, and alarms entirely for free.
|
||||
|
|
@ -154,14 +155,14 @@ ask questions, find resources, and engage with passionate professionals. The tea
|
|||
|
||||
You can also find Netdata on:
|
||||
|
||||
- [Twitter](https://twitter.com/linuxnetdata)
|
||||
- [YouTube](https://www.youtube.com/c/Netdata)
|
||||
- [Reddit](https://www.reddit.com/r/netdata/)
|
||||
- [LinkedIn](https://www.linkedin.com/company/netdata-cloud/)
|
||||
- [StackShare](https://stackshare.io/netdata)
|
||||
- [Product Hunt](https://www.producthunt.com/posts/netdata-monitoring-agent/)
|
||||
- [Repology](https://repology.org/metapackage/netdata/versions)
|
||||
- [Facebook](https://www.facebook.com/linuxnetdata/)
|
||||
- [Twitter](https://twitter.com/linuxnetdata)
|
||||
- [YouTube](https://www.youtube.com/c/Netdata)
|
||||
- [Reddit](https://www.reddit.com/r/netdata/)
|
||||
- [LinkedIn](https://www.linkedin.com/company/netdata-cloud/)
|
||||
- [StackShare](https://stackshare.io/netdata)
|
||||
- [Product Hunt](https://www.producthunt.com/posts/netdata-monitoring-agent/)
|
||||
- [Repology](https://repology.org/metapackage/netdata/versions)
|
||||
- [Facebook](https://www.facebook.com/linuxnetdata/)
|
||||
|
||||
## Contribute
|
||||
|
||||
|
|
|
|||
|
|
@ -1,15 +1,7 @@
|
|||
<!--
|
||||
title: "Troubleshoot Agent-Cloud connectivity issues"
|
||||
sidebar_label: "Troubleshoot Agent-Cloud connectivity issues"
|
||||
description: "A simple guide to troubleshoot occurrences where the Agent is showing as offline after claiming."
|
||||
custom_edit_url: https://github.com/netdata/netdata/edit/master/docs/guides/troubleshoot/troubleshooting-agent-with-cloud-connection.md
|
||||
learn_status: "Published"
|
||||
learn_topic_type: "Tasks"
|
||||
learn_rel_path: "Operations"
|
||||
-->
|
||||
|
||||
# Troubleshoot Agent-Cloud connectivity issues
|
||||
|
||||
Learn how to troubleshoot the Netdata Agent showing as offline after claiming, so you can connect the Agent to Netdata Cloud.
|
||||
|
||||
When you are claiming a node, you might not be able to immediately see it online in Netdata Cloud.
|
||||
This could be due to an error in the claiming process or a temporary outage of some services.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
# View active alerts
|
||||
|
||||
Netdata comes with hundreds of pre-configured health alerts designed to notify you when an anomaly or performance issue affects your node or the applications it runs.
|
||||
Netdata comes with hundreds of pre-configured health alerts designed to notify you when an anomaly or performance issue affects your node or its applications.
|
||||
|
||||
From the Alerts tab you can see all the active alerts in your War Room. You will be presented with a table having information about each alert that is in warning and critical state.
|
||||
You can always sort the table by a certain column by clicking on the name of that column, and use the gear icon on the top right to control which columns are visible at any given time.
|
||||
|
||||
|
||||
|
||||
### Filter alerts
|
||||
## Filter alerts
|
||||
|
||||
From this view, you can also filter alerts with the right hand bar. More specifically you can filter:
|
||||
|
||||
|
|
@ -22,7 +22,7 @@ From this view, you can also filter alerts with the right hand bar. More specifi
|
|||
- Nodes
|
||||
- Filter the alerts based on the nodes that are online, next to each node's name you can see how many alerts the node has, "critical" colored in red and "warning" colored in yellow
|
||||
|
||||
### View alert details
|
||||
## View alert details
|
||||
|
||||
By clicking on the name of an entry of the table you can access that alert's details page, providing you with:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,10 @@
|
|||
# Monitor your infrastructure
|
||||
|
||||
import { Grid, Box, BoxList, BoxListItemRegexLink } from '@site/src/components/Grid/'
|
||||
import { RiExternalLinkLine } from 'react-icons/ri'
|
||||
|
||||
# Monitor your infrastructure
|
||||
|
||||
Learn how to view key metrics, insightful charts, and active alarms from all your nodes, with Netdata Cloud's real-time infrastructure monitoring.
|
||||
|
||||
[Netdata Cloud](https://app.netdata.cloud) provides scalable infrastructure monitoring for any number of distributed
|
||||
nodes running the Netdata Agent. A node is any system in your infrastructure that you want to monitor, whether it's a
|
||||
physical or virtual machine (VM), container, cloud deployment, or edge/IoT device.
|
||||
|
|
@ -10,7 +12,7 @@ physical or virtual machine (VM), container, cloud deployment, or edge/IoT devic
|
|||
The Netdata Agent uses zero-configuration collectors to gather metrics from every application and container instantly,
|
||||
and uses Netdata's [distributed data architecture](https://github.com/netdata/netdata/blob/master/docs/store/distributed-data-architecture.md) to store metrics
|
||||
locally. Without a slow and troublesome centralized data lake for your infrastructure's metrics, you reduce the
|
||||
resources you need to invest in, and the complexity of, monitoring your infrastructure.
|
||||
resources you need to invest in, and the complexity of, monitoring your infrastructure.
|
||||
|
||||
Netdata Cloud unifies infrastructure monitoring by _centralizing the interface_ you use to query and visualize your
|
||||
nodes' metrics, not the data. By streaming metrics values to your browser, with Netdata Cloud acting as the secure proxy
|
||||
|
|
@ -22,7 +24,7 @@ composite charts, and alarm viewing. You'll then learn about the most critical w
|
|||
your nodes to maximize the value you get from Netdata.
|
||||
|
||||
This quickstart assumes you've [installed Netdata](https://github.com/netdata/netdata/edit/master/packaging/installer/README.md)
|
||||
on more than one node in your infrastructure, and connected those nodes to your Space in Netdata Cloud.
|
||||
on more than one node in your infrastructure, and connected those nodes to your Space in Netdata Cloud.
|
||||
|
||||
## Set up your Netdata Cloud experience
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,8 @@
|
|||
# Distributed data architecture
|
||||
|
||||
Netdata uses a distributed data architecture to help you collect and store per-second metrics from any number of nodes.
|
||||
Learn how Netdata's distributed data architecture enables us to store metrics on the edge nodes for security, high performance and scalability.
|
||||
|
||||
This way, it helps you collect and store per-second metrics from any number of nodes.
|
||||
Every node in your infrastructure, whether it's one or a thousand, stores the metrics it collects.
|
||||
|
||||
Netdata Cloud bridges the gap between many distributed databases by _centralizing the interface_ you use to query and
|
||||
|
|
@ -71,6 +73,3 @@ or [filtering by hostname/service](https://github.com/netdata/netdata/blob/maste
|
|||
store configured alarms, their status, and a list of active collectors.
|
||||
|
||||
Netdata does not and never will sell your personal data or data about your deployment.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,12 @@
|
|||
# Install Netdata
|
||||
|
||||
import { OneLineInstallWget, OneLineInstallCurl } from '@site/src/components/OneLineInstall/'
|
||||
import { InstallRegexLink, InstallBoxRegexLink } from '@site/src/components/InstallRegexLink/'
|
||||
import Tabs from '@theme/Tabs';
|
||||
import TabItem from '@theme/TabItem';
|
||||
|
||||
# Install Netdata
|
||||
|
||||
This document will guide you through installing the open-source Netdata monitoring Agent on Linux, Docker, Kubernetes, and many others, often with one command.
|
||||
|
||||
## Get started
|
||||
|
||||
Netdata is a free and open-source (FOSS) monitoring agent that collects thousands of hardware and software metrics from
|
||||
|
|
@ -19,7 +21,7 @@ Docker), and many other operating systems (FreeBSD, macOS), with no `sudo` requi
|
|||
|
||||
To install Netdata in minutes on your platform:
|
||||
|
||||
1. Sign up to https://app.netdata.cloud/
|
||||
1. Sign up to <https://app.netdata.cloud/>
|
||||
2. You will be presented with an empty space, and a prompt to "Connect Nodes" with the install command for each platform
|
||||
3. Select the platform you want to install Netdata to, copy and paste the script into your node's terminal, and run it
|
||||
|
||||
|
|
@ -184,16 +186,16 @@ the community helps fix any bugs that might have been introduced in previous rel
|
|||
|
||||
**Pros of using nightly releases:**
|
||||
|
||||
- Get the latest features and bug fixes as soon as they're available
|
||||
- Receive security-related fixes immediately
|
||||
- Use stable, fully-tested code that's always improving
|
||||
- Leverage the same Netdata experience our community is using
|
||||
- Get the latest features and bug fixes as soon as they're available
|
||||
- Receive security-related fixes immediately
|
||||
- Use stable, fully-tested code that's always improving
|
||||
- Leverage the same Netdata experience our community is using
|
||||
|
||||
**Pros of using stable releases:**
|
||||
|
||||
- Protect yourself from the rare instance when major bugs slip through our testing and negatively affect a Netdata
|
||||
- Protect yourself from the rare instance when major bugs slip through our testing and negatively affect a Netdata
|
||||
installation
|
||||
- Retain more control over the Netdata version you use
|
||||
- Retain more control over the Netdata version you use
|
||||
|
||||
### Anonymous statistics
|
||||
|
||||
|
|
@ -256,5 +258,3 @@ both.
|
|||
Our current build process has some issues when using certain configurations of the `clang` C compiler on Linux. See [the
|
||||
section on `nonrepresentable section on output`
|
||||
errors](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/manual.md#nonrepresentable-section-on-output-errors) for a workaround.
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue