ba7e2bf39 · cryptotaxi247/netdata-1

@@ -41,7 +41,7 @@ For more information see [Deployment Strategies](https://github.com/netdata/netd

41

42 Netdata has been architected to minimize resource consumption while maximizing observability capabilities. This efficiency is achieved through several key design decisions:

43

44 -- **Storage Optimization**: Industry-leading compression achieving ~0.5 bytes per sample on disk for high-resolution data

44 +- **Storage Optimization**: Industry-leading compression achieving ~0.6 bytes per sample on disk for high-resolution data

45 - **Edge Computing**: Distributed architecture keeps data processing close to its source, reducing bandwidth and central processing requirements - Netdata distributes the code instead of centralizing the data

46 - **Intelligent ML**: Machine learning runs as low-priority background tasks, automatically yielding resources when needed for data collection. See [AI & ML Features](https://github.com/netdata/netdata/blob/master/docs/category-overview-pages/machine-learning-and-assisted-troubleshooting.md)

47 - **Built-in Scalability**: Native clustering and high-availability features enable organizations to scale horizontally without architectural changes. See [Observability Centralization Points](https://github.com/netdata/netdata/blob/master/docs/observability-centralization-points/README.md).

@@ -97,10 +97,10 @@ Netdata users have multiple options to deploy Netdata on their systems. Netdata

97

98 ### Agent and Parent Deployment Options

99

100 -**1. Configuration Management Tools**: Use Ansible, Puppet, Chef, Salt, Terraform

101 -**2. Container Deployment**: Use official Docker images

102 -**3. Native Package Management**: Use native GPG-signed packages for Debian, Ubuntu, Red Hat, CentOS, SUSE, etc., with the ability to mirror Netdata repositories internally for air-gapped environments

103 -**4. One-Line Installation with Auto-Updates**: Single command installation that configures automatic updates, with a choice of release channels: stable (recommended) or nightly

100 +1. **Configuration Management Tools**: Use Ansible, Puppet, Chef, Salt, Terraform

101 +2. **Container Deployment**: Use official Docker images

102 +3. **Native Package Management**: Use native GPG-signed packages for Debian, Ubuntu, Red Hat, CentOS, SUSE, etc., with the ability to mirror Netdata repositories internally for air-gapped environments

103 +4. **One-Line Installation with Auto-Updates**: Single command installation that configures automatic updates, with a choice of release channels: stable (recommended) or nightly

104

105 **Note**: Netdata Parents use the same software as Agents with different configuration. All deployment methods apply to both.

106

@@ -136,9 +136,9 @@ Netdata scales horizontally. There is no limit on how large a Netdata monitored

136

137 For data ingestion and storage, there is no limit, theoretical or practical. When using standalone agents, each agent is independent of the others. When using parent-child agents, each parent is sized independently of the others and the system scales by adding more parents.

138

139 -Practical limits exist when querying observability data, mainly due to the amount of information web browsers and aggregation points can reasonably handle at once. The system becomes slower depending on the amount of information queried at once (i.e. how many nodes, instances, time-series appear on the same chart or view).

139 +Practical limits exist when querying observability data, mainly due to the amount of information web browsers and aggregation points can reasonably handle at once. The system becomes slower depending on the amount of information queried at once (i.e. how many nodes, instances, time-series appear on the same chart or view), similar to all observability platforms (not Netdata specific).

140

141 -Due to the distributed nature of the architecture, Netdata responsiveness is usually significantly better compared to other monitoring solutions. Still, it is influenced by the amount of data queried at once.

141 +Due to the distributed nature of the architecture (parallel independent execution of smaller queries), Netdata responsiveness is usually significantly better compared to other monitoring solutions. Still, it is influenced by the amount of data queried at once.

142

143 ## Impact on the Monitored Infrastructure

144

Update netdata-enterprise-evaluation-corrected.md