a399128dbf
* added parser for durations
* preliminary work for timeframes
* Update CMakeLists.txt
* updated parsing and generation for durations
* renames
* report parser errors; added compatibility to existing config_parse_duration()
* duration parsing is used on most netdata.conf and stream.conf entries
* more uses of duration parsing; simplification of stream.conf
* code cleanup
* more duration changes
* added html playground
* improved js code
* duration parsing applied to dbengine retention
* fixed doc
* simplified logic; added size parser
* added parsing for sizes
* renames and documentation updates
* hide appconfig internals from the rest of netdata
* fix crash on cleanup of streaming receivers
* fix buffer overflow in gorilla compression
* config return values are const
* ksm set to auto
* support reformatting migrated values
* removed obsolete metrics correlations settings
* split appconfig to multiple files
* durations documentation
* sizes documentation
* added backward compatibility in retention configuration
* provide description on migrations and reformattings
* config options are now a double linked list
* config sections are now a double linked list; config uses spinlocks; code cleanup and renames
* added data type to all config options
* update data types
* split appconfig api to multiple files
* code cleanup and renames
* removed size units above PiB
* Revert "fix buffer overflow in gorilla compression"
This reverts commit
|
||
|---|---|---|
| .. | ||
| clustering-and-high-availability-of-netdata-parents.md | ||
| configuration.md | ||
| faq.md | ||
| README.md | ||
| replication-of-past-samples.md | ||
| sizing-netdata-parents.md | ||
Metrics Centralization Points (Netdata Parents)
Netdata Streaming and Replication copies the recent past samples (replication) and in real-time all new samples collected (streaming) from production systems (Netdata Children) to metrics centralization points (Netdata Parents). The Netdata Parents then maintain the database for these metrics, according to their retention settings.
Each production system (Netdata Child) can stream to only one Netdata Parent at a time. The configuration allows configuring multiple Netdata Parents for high availability, but only the first found working will be used.
Netdata Parents receive metric samples from multiple production systems (Netdata Children) and have the option to re-stream them to another Netdata Parent. This allows building an infinite hierarchy of Netdata Parents. It also enables the configuration of Netdata Parents Clusters, for high availability.
| Feature | Netdata Child (production system) | Netdata Parent (centralization point) |
|---|---|---|
| Metrics Retention | Can be minimized, or switched to mode ram or alloc to save resources. Some retention is required in case network errors introduce disconnects. |
Common retention settings for all systems aggregated to it. |
| Machine Learning | Can be disabled (enabled by default). | Runs Anomaly Detection for all systems aggregated to it. |
| Alerts & Notifications | Can be disabled (enabled by default). | Runs health checks and sends notifications for all systems aggregated to it. |
| API and Dashboard | Can be disabled (enabled by default). | Serves the dashboard for all systems aggregated to it, using its own retention. |
| Exporting Metrics | Not required (enabled by default). | Exports the samples of all metrics collected by the systems aggregated to it. |
| Netdata Functions | Netdata Child must be online. | Forwards Functions requests to the Children connected to it. |
| Connection to Netdata Cloud | Not required. | Each Netdata Parent registers to Netdata Cloud all systems aggregated to it. |
Supported Configurations
For Netdata Children:
- Full: Full Netdata functionality is available at the Children. This means running machine learning, alerts, notifications, having the local dashboard available, and generally all Netdata features enabled. This is the default.
- Thin: The Children are only collecting and forwarding metrics to a Parent. Some local retention may exist to avoid missing samples in case of network issues or Parent maintenance, but everything else is disabled.
For Netdata Parents:
- Standalone: The Parent is standalone, either the only Parent available in the infrastructure, or the top-most of an hierarchy of Parents.
- Cluster: The Parent is part of a cluster of Parents, all having the same data, from the same Children. A Cluster of Parents offers high-availability.
- Proxy: The Parent receives metrics and stores them locally, but it also forwards them to a Grand Parent.
A Cluster is configured as a number of circular Proxies, ie. each of the nodes in a cluster has all the others configured as its Parents. So, if multiple levels of metrics centralization points (Netdata Parents) are required, only the top-most level can be a cluster.
Best Practices
Refer to Best Practices for Observability Centralization Points.