[Support] Data-Monkey - netdata

[frodr]

22 hours ago, frodr said:

I'm struggling with the basics here. How to get the node connected to the Could Account? Trying to "Sign in" I get a mail with a link to the Cloud Account, but how to link the node?

 

Anyone?

 

//

 

 

Please.....

[frodr]

6 hours ago, frodr said:

 

 

Please.....

 

By deleting the Netdata app, and run the dockers script from the cloud account, I was able to include the node to the cloud account. 

[doctortt]

On 5/31/2023 at 8:13 AM, TexasUnraid said:

I have no idea but I am interested in what you find out. I used hddtemp for awhile and it works but I found it broke drive spinddown. I would like to get drive temps back into netdata.

The better place to ask about this type of stuff is the github, they have been real good when I have had questions over there.

 

Absolutely no luck at all. I posted the question on Netadata's github for some time and nobody responded, not even the Netdata team. Unbelievable. I also tried to ask on discord and nobody knows.  I'm very surprised that for those who use netdata, they don't even care about monitoring hdd temp? 

[TexasUnraid]

8 hours ago, doctortt said:

 

Absolutely no luck at all. I posted the question on Netadata's github for some time and nobody responded, not even the Netdata team. Unbelievable. I also tried to ask on discord and nobody knows.  I'm very surprised that for those who use netdata, they don't even care about monitoring hdd temp? 

Yeah, I was surprised by this as well, seems like one of the more vital things I would want to monitor, all I really look at in netdata are temps, fan speeds and then the basic cpu/ram/disk etc

[Ether Wrangler]

If any of you are still looking to set this up to work with NetData Cloud:

• Login to your cloud account and under Integrations > Deploy > Docker & Kubernetes > click Docker
  • Copy the Docker CLI output and paste it into Notepad or a text editor
• Back in Unraid either edit the settings on your existing NetData docker or add one
• Click "Add another Path, Port, Variable, Label or Device"
  • Change the type to Variable
  • For Name and Key paste in NETDATA_CLAIM_TOKEN
  • For Value paste in your claim token from your text file
• Repeat adding variables and values for NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS

[singularity098]

My Netdata starts and crashes immediately due to too many errors.  I've used it for like over a year and it just started doing this a couple of weeks ago.  I have no idea what's changed and why this is happening. 

 

I didn't change anything in my Docker template mappings.  I am on Unraid 6.11.5. 

 

2023-08-16 21:35:59: go.d ERROR: logstash[local] check failed
2023-08-16 21:35:59: go.d WARNING: k8s_kubelet[k8s_kubelet] error on reading service account token from '/var/run/secrets/kubernetes.io/serviceaccount/token': open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2023-08-16 21:35:59: go.d ERROR: k8s_kubelet[k8s_kubelet] Get "http://127.0.0.1:10255/metrics": dial tcp 127.0.0.1:10255: connect: connection refused
2023-08-16 21:35:59: go.d ERROR: k8s_kubelet[k8s_kubelet] check failed
2023-08-16 21:35:59: go.d WARNING: k8s_kubelet[k8s_kubelet] error on reading service account token from '/var/run/secrets/kubernetes.io/serviceaccount/token': open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
2023-08-16 21:35:59: go.d ERROR: k8s_kubelet[k8s_kubelet] Get "https://localhost:10250/metrics": dial tcp 127.0.0.1:10250: connect: connection refused
2023-08-16 21:35:59: go.d ERROR: k8s_kubelet[k8s_kubelet] check failed
2023-08-16 21:35:59: go.d ERROR: nginx[local] http://127.0.0.1/basic_status returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: nginx[local] check failed
2023-08-16 21:35:59: go.d ERROR: nginx[local] http://localhost/stub_status returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: nginx[local] check failed
2023-08-16 21:35:59: go.d ERROR: nginx[local] http://127.0.0.1/stub_status returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: nginx[local] check failed
2023-08-16 21:35:59: go.d ERROR: nginx[local] http://127.0.0.1/nginx_status returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: nginx[local] check failed
2023-08-16 21:35:59: go.d ERROR: nginx[local] http://127.0.0.1/status returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: nginx[local] check failed
2023-08-16 21:35:59: go.d ERROR: lighttpd[local] http://localhost/server-status?auto returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: lighttpd[local] check failed
2023-08-16 21:35:59: go.d ERROR: lighttpd[local] http://127.0.0.1/server-status?auto returned HTTP status 404
2023-08-16 21:35:59: go.d ERROR: lighttpd[local] check failed
2023-08-16 21:35:59: netdata INFO  : P[proc] : cpufreq is using /host/sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state
2023-08-16 21:35:59: netdata INFO  : P[proc] : Using now_boottime_usec() for uptime (dt is 7 ms)
2023-08-16 21:35:59: netdata ERROR : P[proc] : Cannot read pressure information from /host/proc/pressure/cpu. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : Cannot read pressure information from /host/proc/pressure/memory. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : Cannot read pressure information from /host/proc/pressure/io. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : PROCFILE: Cannot open file '/host/proc/net/wireless' (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : PROCFILE: Cannot open file '/host/proc/net/sctp/snmp' (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : PROCFILE: Cannot open file '/host/proc/net/ip_vs_stats' (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : PROCFILE: Cannot open file '/host/proc/net/stat/synproxy' (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop0', 7:0): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop0', 7:0): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop0', 7:0): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop1', 7:1): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop1', 7:1): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop1', 7:1): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop2', 7:2): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop2', 7:2): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop2', 7:2): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop3', 7:3): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop3', 7:3): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop3', 7:3): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop4', 7:4): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop4', 7:4): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop4', 7:4): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop5', 7:5): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop5', 7:5): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop5', 7:5): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop6', 7:6): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop6', 7:6): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop6', 7:6): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop7', 7:7): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop7', 7:7): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('loop7', 7:7): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda', 8:0): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda', 8:0): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda', 8:0): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda1', 8:1): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda1', 8:1): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sda1', 8:1): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1', 259:0): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1', 259:0): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1', 259:0): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1p1', 259:1): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1p1', 259:1): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('nvme0n1p1', 259:1): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb', 8:16): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb', 8:16): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb', 8:16): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb1', 8:17): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb1', 8:17): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdb1', 8:17): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc', 8:32): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc', 8:32): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc', 8:32): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc1', 8:33): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc1', 8:33): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdc1', 8:33): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd', 8:48): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd', 8:48): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd', 8:48): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd1', 8:49): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd1', 8:49): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sdd1', 8:49): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/host/dev/mapper'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/host/dev/disk/by-label'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata ERROR : P[proc] : DEVICE-MAPPER ('sde', 8:64): Cannot open directory '/host/dev/vx/dsk'. (errno 2, No such file or directory)
2023-08-16 21:35:59: netdata LOG FLOOD PROTECTION too many logs (201 logs in 1 seconds, threshold is set to 200 logs in 1200 seconds). Preventing more logs from process 'netdata' for 1199 seconds.
2023-08-16 21:35:59: apps.plugin ERROR : APPS_READER : Received error on stdin. (errno 22, Invalid argument)
EOF found in spawn pipe.

 

Edited August 19, 2023 by singularity098

[sastromo]

On 8/19/2023 at 2:06 AM, Ether Wrangler said:

If any of you are still looking to set this up to work with NetData Cloud:

• Login to your cloud account and under Integrations > Deploy > Docker & Kubernetes > click Docker
  • Copy the Docker CLI output and paste it into Notepad or a text editor
• Back in Unraid either edit the settings on your existing NetData docker or add one
• Click "Add another Path, Port, Variable, Label or Device"
  • Change the type to Variable
  • For Name and Key paste in NETDATA_CLAIM_TOKEN
  • For Value paste in your claim token from your text file
• Repeat adding variables and values for NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS

 

Thank you!

[Zerreth]

On 8/19/2023 at 3:32 PM, singularity098 said:

My Netdata starts and crashes immediately due to too many errors.  I've used it for like over a year and it just started doing this a couple of weeks ago.  I have no idea what's changed and why this is happening. 

I'm in the same boat when trying to install it on another unraid server whist I got a working instance on my media unraid server. (v1.42.0-95-nightly on the working one with docker vdisk, docker folders on the other that isn't working and latest nightly) No clue what's wrong, the configuration is identical. (except for the cloud connection token ofc)

Mapping

/var/log/netdata

to e.g. /mnt/user/appata/netdata/log/netdata (or wherever) so I can inspect the logs more easily & compairing logs with the working server:

2023-08-27 22:00:15: apps.plugin ERROR : APPS_READER : Received error on stdin. (errno 22, Invalid argument)

Seems to be that it's trying to open a file but the file path is invalid/deesn't exist.

Edited August 27, 2023 by Zerreth

[Daniel15]

How do you edit the configs when using this Docker container? For example, I want to enable more plugins. With regular Netdata, you'd run `sudo ./edit-config python.d/foo.conf`. What's the equivalent here?

[Zerreth]

15 hours ago, Daniel15 said:

How do you edit the configs when using this Docker container? For example, I want to enable more plugins. With regular Netdata, you'd run `sudo ./edit-config python.d/foo.conf`. What's the equivalent here?

Presumably you would map `/etc/netdata` to a location in your appdata share (e.g.  /mnt/user/System/Appdata/netdata/config/netdata - Note my appdata is in a slightly different location.) And then just edit the netdata.conf file it spits out in there with a text editor.

[Daniel15]

22 hours ago, Zerreth said:

And then just edit the netdata.conf file it spits out in there with a text editor.

You normally need to edit files other than the netdata.conf file to enable extra graphs - each collector has its own separate config file. Netdata has a script called edit-config that'll copy the default config from the Netdata installation into /etc/netdata, after which you'd edit it. I don't know how to get the default configs to edit when it's running in Docker, though. I guess I could copy them from another server I've got that's running Netdata. Maybe getting a shell in the Docker container itself then running edit-data will work, as long as /etc/netdata is mapped properly.

Edited September 3, 2023 by Daniel15

[Ether Wrangler]

On 8/22/2023 at 7:01 PM, sastromo said:

 

Thank you!

 

One other thing I noticed after a couple of reboots is that if you don't persist some of the directories in this docker, it will show up as a new device in NetData Cloud.  I added these mappings to fix that and get the OS to show correctly (Slackware) and to fix group/user enumeration.

 

[local-loading6497]

can somone help, my unraid netdata needs to be re-added as an "agent" / "node" after every reboot or restart. as i have alot of devices i really dont want to re-add every day when it updats.

 

how do i set this up to be constantly one of my nodes? without having to go through the session ID every time !

[sastromo]

On 9/8/2023 at 11:35 PM, Ether Wrangler said:

 

One other thing I noticed after a couple of reboots is that if you don't persist some of the directories in this docker, it will show up as a new device in NetData Cloud.  I added these mappings to fix that and get the OS to show correctly (Slackware) and to fix group/user enumeration.

 

 

thank you!!

no more new devices

 

[Ether Wrangler]

On 9/13/2023 at 3:55 PM, local-loading6497 said:

can somone help, my unraid netdata needs to be re-added as an "agent" / "node" after every reboot or restart. as i have alot of devices i really dont want to re-add every day when it updats.

 

how do i set this up to be constantly one of my nodes? without having to go through the session ID every time !

 

If you mean having to add it back to the cloud every time, check my post above yours.  That shows the additional mappings to add to keep that from happening.

 

I'm working on submitting a pull request to roland to update this template with those values.

[wam731]

Random Question im am on the latest unraid version and have been considering installing netdata.  At the begining of this forum i saw a mention of limiting the log file size and number, is that still a thing and if so how would i go about doing that?

[Ether Wrangler]

On 10/12/2023 at 7:47 PM, wam731 said:

Random Question im am on the latest unraid version and have been considering installing netdata.  At the begining of this forum i saw a mention of limiting the log file size and number, is that still a thing and if so how would i go about doing that?

 

The template has that taken care of with an argument in Extra Parameters.  This template is ready to go if you want NetData locally.  If you want NetData Cloud to work properly, you'll need to add the variables and path mappings from these two posts I made.

 

On 9/8/2023 at 5:35 PM, Ether Wrangler said:

 

One other thing I noticed after a couple of reboots is that if you don't persist some of the directories in this docker, it will show up as a new device in NetData Cloud.  I added these mappings to fix that and get the OS to show correctly (Slackware) and to fix group/user enumeration.

 

 

On 8/18/2023 at 8:06 PM, Ether Wrangler said:

If any of you are still looking to set this up to work with NetData Cloud:

• Login to your cloud account and under Integrations > Deploy > Docker & Kubernetes > click Docker
  • Copy the Docker CLI output and paste it into Notepad or a text editor
• Back in Unraid either edit the settings on your existing NetData docker or add one
• Click "Add another Path, Port, Variable, Label or Device"
  • Change the type to Variable
  • For Name and Key paste in NETDATA_CLAIM_TOKEN
  • For Value paste in your claim token from your text file
• Repeat adding variables and values for NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS

 

[Daniel15]

This template is missing a bunch of Docker bind mounts, for example /var/lib/netdata (which stores the database so data is retained when Netdata is restarted). This is the docker command in Netdata's official documentation:

docker run -d --name=netdata \
  --pid=host \
  --network=host \
  -v netdataconfig:/etc/netdata \
  -v netdatalib:/var/lib/netdata \
  -v netdatacache:/var/cache/netdata \
  -v /etc/passwd:/host/etc/passwd:ro \
  -v /etc/group:/host/etc/group:ro \
  -v /proc:/host/proc:ro \
  -v /sys:/host/sys:ro \
  -v /etc/os-release:/host/etc/os-release:ro \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  --restart unless-stopped \
  --cap-add SYS_PTRACE \
  --cap-add SYS_ADMIN \
  --security-opt apparmor=unconfined \
  netdata/netdata

 

Also, if you want to claim it on Netdata Cloud, you need to add NETDATA_CLAIM_TOKEN, NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS, which can be found in Netdata Cloud by going to the nodes tab, clicking "Add node", then going to the Docker tab.

[dopeytree]

Latest update causes random drive spin ups (stops when contains is stopped).

[Daniel15]

19 hours ago, dopeytree said:

Latest update causes random drive spin ups (stops when contains is stopped).

 

If you have the hddtemp integration enabled, I think it's a known issue that reading the drive temperature spins up the drive (that's an issue with hddtemp, not with Netdata)

[Ether Wrangler]

On 10/14/2023 at 1:56 PM, Daniel15 said:

This template is missing a bunch of Docker bind mounts, for example /var/lib/netdata (which stores the database so data is retained when Netdata is restarted). This is the docker command in Netdata's official documentation:

docker run -d --name=netdata \
  --pid=host \
  --network=host \
  -v netdataconfig:/etc/netdata \
  -v netdatalib:/var/lib/netdata \
  -v netdatacache:/var/cache/netdata \
  -v /etc/passwd:/host/etc/passwd:ro \
  -v /etc/group:/host/etc/group:ro \
  -v /proc:/host/proc:ro \
  -v /sys:/host/sys:ro \
  -v /etc/os-release:/host/etc/os-release:ro \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  --restart unless-stopped \
  --cap-add SYS_PTRACE \
  --cap-add SYS_ADMIN \
  --security-opt apparmor=unconfined \
  netdata/netdata

 

Also, if you want to claim it on Netdata Cloud, you need to add NETDATA_CLAIM_TOKEN, NETDATA_CLAIM_URL and NETDATA_CLAIM_ROOMS, which can be found in Netdata Cloud by going to the nodes tab, clicking "Add node", then going to the Docker tab.

 

A change request was merged in two days ago adding all of the missing mounts as well as the needed cloud claim tokens.

[Terebi]

To get the netdata random ID to connect to the cloud, you have to run look up the netdata_random_session_id from inside the netdata container console, not the unraid console

[bombz]

Hello, 

 

Reaching out as I just came across this docker image looking for a method to monitors power wattage and electracy usage.
I haven't stumbled across this yet within this docker app. However, I must say it's quite incredible application here! I will keep investigating as I just deployed this image, there is A TON of useful monitoring tools here!

Props to the dev-team!

Thank you!

[Przemek]

Does anybody is able to see Wireguard VPN stats in netdata? I can't see anything and additionally when I run debug on the wireguard collector I see that

 

cd /usr/libexec/netdata/plugins.d    
./go.d.plugin -d -m wireguard
[...]
ERR wireguard/wireguard.go:71 retrieving WireGuard devices: operation not permitted collector=wireguard job=wireguard
ERR module/job.go:229 check failed collector=wireguard job=wireguard
REPORT_JOB_STATUS 'wireguard' 'wireguard_496428254644300562' 'error' 0 'job detection failed, stopping it'

 

[stottle]

On 3/8/2020 at 10:37 PM, mattgob86 said:

Is there something that needs to happen to get nvidia SMI data to work in this new docker?

I didn't see an answer posted, but per a post in another netdata support thread, the nvidia-smi support was moved from python.d.conf to go.d.conf (and set to "no" instead of "yes").

 

I was able to get Nvidia visualizations by changing (in go.conf.d)

#  nvidia_smi: no

to

  nvidia_smi: yes

 

I needed to add the parameter/value NVIDIA_VISIBLE_DEVICES / 'all' to the docker template and append `--runtime=nvidia` to Extra Parameters as well.

 

I used the following to create/edit the config file (from the post linked above):

On 7/27/2023 at 9:14 PM, D34DC3N73R said: 

If you're using a new configuration or you've disabled the python nvidia-smi, then you can edit go.d.conf

docker exec -it netdata bash
cd /etc/netdata
./edit-config go.d.conf