mirror of
https://github.com/netdata/netdata.git
synced 2025-04-10 16:17:36 +00:00
Update netdata-agent-security.md (#17738)
* Update netdata-agent-security.md * Update backup-and-restore-an-agent.md * Update backup-and-restore-an-agent.md * Update netdata-agent-security.md * Apply suggestions from code review * Update docs/netdata-agent/backup-and-restore-an-agent.md --------- Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>
This commit is contained in:
parent
18a88fd856
commit
e9b53787db
2 changed files with 9 additions and 0 deletions
docs
|
@ -1,5 +1,9 @@
|
|||
# Backing up a Netdata Agent
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Users are responsible for backing up, recovering, and ensuring their data's availability because Netdata stores data locally on each system due to its decentralized architecture.
|
||||
|
||||
## Introduction
|
||||
|
||||
When preparing to backup a Netdata Agent it is worth considering that there are different kinds of data that you may wish to backup independently or all together:
|
||||
|
|
|
@ -10,6 +10,11 @@ databases, sent to upstream Netdata servers, or archived to external time-series
|
|||
|
||||
## User Data Protection
|
||||
|
||||
> **Note**
|
||||
>
|
||||
> Users are responsible for backing up, recovering, and ensuring their data's availability because Netdata stores data locally on each system due to its decentralized architecture.
|
||||
|
||||
|
||||
The Netdata Agent is programmed to safeguard user data. When collecting data, the raw data does not leave the host. All
|
||||
plugins, even those running with escalated capabilities or privileges, perform a hard-coded data collection job. They do
|
||||
not accept commands from Netdata, and the original application data collected do not leave the process they are
|
||||
|
|
Loading…
Add table
Reference in a new issue