![]() |
4 years ago | |
---|---|---|
.. | ||
tests | 5 years ago | |
Makefile.am | 5 years ago | |
README.md | 4 years ago | |
aclk_common.c | 5 years ago | |
aclk_common.h | 5 years ago | |
aclk_lws_https_client.c | 5 years ago | |
aclk_lws_https_client.h | 5 years ago | |
aclk_lws_wss_client.c | 5 years ago | |
aclk_lws_wss_client.h | 5 years ago | |
agent_cloud_link.c | 4 years ago | |
agent_cloud_link.h | 4 years ago | |
mqtt.c | 4 years ago | |
mqtt.h | 5 years ago |
The Agent-Cloud link (ACLK) is the mechanism responsible for connecting a Netdata Agent to Netdata Cloud. The ACLK uses MQTT over secure websockets to first create, persist, encrypt the connection, and then enable the features found in Netdata Cloud. No data is exchanged with Netdata Cloud until you claim a node.
Read our claiming documentation for a guide for claiming a node using the ACLK and additional troubleshooting and reference information.
The ACLK is enabled by default and automatically configured if the prerequisites installed correctly. You can see this
in the [cloud]
section of netdata.conf
.
[cloud]
cloud base url = https://app.netdata.cloud
If your Agent needs to use a proxy to access the internet, you must set up a proxy for claiming.
You have two options if you prefer to disable the ACLK and not use Netdata Cloud:
Pass --disable-cloud
to netdata-installer.sh
during installation. When you pass this parameter, the installer
does not download or compile any extra libraries, and the Agent behaves as though the ACLK, and thus Netdata Cloud,
does not exist. ACLK functionality is available in the Agent but remains fully inactive.
Change a runtime setting in your netdata.conf
file. This setting only stops the Agent from attempting any
connection via the ACLK, but does not prevent the installer from downloading and compiling the ACLK's dependencies.
[global]
netdata cloud = disable