archive/netdata_netdata
0
0
Fork 0
mirror of https://github.com/netdata/netdata.git synced 2025-05-17 14:42:21 +00:00
Code Issues Projects Releases Wiki Activity

Capitalize the word "Agent" ()

Browse source 
* Capitalize the word Agent

* yaml -> json

* fix uppercase keys

* json update
This commit is contained in:
Fotis Voutsas 2024-11-20 15:27:03 +02:00 • committed by GitHub
parent d8daa5527a
commit 32a6cd38e7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
90 changed files with 250 additions and 257 deletions
docs/netdata-agent/sizing-netdata-agents
bandwidth-requirements.md

2
docs/netdata-agent/sizing-netdata-agents/bandwidth-requirements.md
View file

@ -44,4 +44,4 @@ The information transferred to Netdata Cloud is:
This is not a constant stream of information. Netdata Agents update Netdata Cloud only about status changes on all the above (e.g., an alert being triggered, or a metric stopped being collected). So, there is an initial handshake and exchange of information when Netdata starts, and then there only updates when required.
Of course, when you view Netdata Cloud dashboards that need to query the database a Netdata agent maintains, this query is forwarded to an agent that can satisfy it. This means that Netdata Cloud receives metric samples only when a user is accessing a dashboard and the samples transferred are usually aggregations to allow rendering the dashboards.
Of course, when you view Netdata Cloud dashboards that need to query the database a Netdata Agent maintains, this query is forwarded to an Agent that can satisfy it. This means that Netdata Cloud receives metric samples only when a user is accessing a dashboard and the samples transferred are usually aggregations to allow rendering the dashboards.