Enabled more collectors on MacOS, but not shown after restart

Help
,
1

Hi there,

I tried to enable more collectors on my Netdata on MacOS 13 Ventura as described on Enable or configure a collector | Learn Netdata
My netdata config dir is /usr/local/etc/netdata, so I copied some files from my Netdata on Linux/Docker, but after restart no new collectors were shown:

go.d/
go.d/dns_query.conf
health.d/
health.d/dns_query.conf
health.d/go.d.plugin.conf

This is how it looks after restarting:

image
image326×614 11.6 KB

And this is how it should/could look like (taken from some of my other netdata):

image
image406×1002 59.4 KB

My Environment/Browser/Agent’s version etc:
MacOS 13 Ventura, Netdata stable 1.37.0 from brew

Please advice what’s different on MacOS or what I haven’t understand from the docu. Thanks a lot!

2

My go.d/dns_query.conf

Summary 
jobs:
- name: int_dns
  update_every: 10
  domains:
    - web.de
  servers:
    - 172.23.104.73
    - 172.23.104.74
- name: ext_cloudflare
  update_every: 10
  domains:
    - web.de
  servers:
    - 1.0.0.1
    - 1.1.1.1
- name: ext_google
  update_every: 10
  domains:
    - web.de
  servers:
    - 8.8.4.4
    - 8.8.8.8
- name: ext_nextdns
  update_every: 10
  domains:
    - web.de
  servers:
    - 45.90.28.39
    - 45.90.30.39
- name: ext_vodafone
  update_every: 10
  domains:
    - web.de
  servers:
    - 192.168.0.1
    - 80.69.96.12
- name: ext_dnswatch
  update_every: 10
  domains:
    - web.de
  servers:
    - 84.200.69.80
    - 84.200.70.40
- name: ext_quad9
  update_every: 10
  domains:
    - web.de
  servers:
    - 9.9.9.11
    - 149.112.112.11
- name: ext_opendns
  update_every: 10
  domains:
    - web.de
  servers:
    - 208.67.220.220
    - 208.67.222.222
- name: freifunk_mue
  update_every: 10
  domains:
    - web.de
  servers:
    - 5.1.66.255
    - 185.150.99.255
- name: dismail.de
  update_every: 10
  domains:
    - web.de
  servers:
    - 80.241.218.68
    - 159.69.114.157
- name: dnsforge.de
  update_every: 10
  domains:
    - web.de
  servers:
    - 176.9.93.198
    - 176.9.1.117
- name: adguard_with_filter
  update_every: 10
  domains:
    - web.de
  servers:
    - 94.140.14.14
    - 94.140.15.15
- name: adguard_without_filter
  update_every: 10
  domains:
    - web.de
  servers:
    - 94.140.14.140
    - 94.140.14.141
- name: njalla
  update_every: 10
  domains:
    - web.de
  servers:
    - 95.215.19.53
- name: digitalcourage
  update_every: 10
  domains:
    - web.de
  servers:
    - 46.182.19.48

My health.d/dns_query.conf

Summary 
 query failure
 template: dns_query_time_query_time
       on: dns_query_time.query_time
    class: Latency
     type: DNS
component: DNS
   lookup: average -10s unaligned foreach *
    units: ms
    #every: 10s
    every: 30s
     #warn: $this == nan
    delay: up 20s down 5m multiplier 1.5 max 1h
     #info: average DNS query round trip time over the last 10 seconds
     info: average DNS query round trip time over the last 30 seconds
       to: sysadmin

My health.d/go.d.plugin.conf

Summary 
 template: go.d_job_last_collected_secs
       on: netdata.go_plugin_execution_time
    class: Error
     type: Netdata
component: go.d.plugin
   module: *
     calc: $now - $last_collected_t
    units: seconds ago
    ###every: 10s
    ### due to many "Warning, go.d_job_last_collected_secs = 58 seconds ago, on other instance"
    every: 60s
     ###warn: $this > (($status >= $WARNING)  ? ($update_every) : ( 5 * $update_every))
     warn: $this > (($status >= $WARNING)  ? ($update_every) : (10 * $update_every))
     crit: $this > (($status == $CRITICAL) ? ($update_every) : (60 * $update_every))
    delay: down 5m multiplier 1.5 max 1h
     info: number of seconds since the last successful data collection
       ### "Warning, go.d_job_last_collected_secs = 61 seconds ago, on 216485c8b61c"
       ###to: webmaster
       to: silent
3

I’d first check the [plugins] section in netdata.conf, in case you have differences between the two nodes there. Then check charts.d.conf, for enabled/disabled collectors.

Sensors doesn’t work the same on every machine, so we have two different collectors to try and cover most case. Start here, it has the link to the other collector too.

DNS should definitely be working on Mac if the plugin and the collector are enabled. I would run it in debug mode, to see what it complains about.