Specify an Alarm Configuration Example

[cheyngoodman]

I deploy NetData to a QNAP using:

CLAIM_TOKEN="<SECRET>"
helm repo add netdata https://netdata.github.io/helmchart
helm install netdata netdata/netdata \
--set parent.claiming.enabled="true" \
--set parent.claiming.token="$CLAIM_TOKEN" \
--set child.claiming.enabled="true" \
--set child.claiming.token="$CLAIM_TOKEN"

QNAP OS has two conflicts with Netdata checks netdata/netdata#11180
and netdata/netdata#14848

It seems for QNAP systems, netdata.conf should be updated to disable the false positives:

[health]
    enabled alarms = !system_clock_sync_state !mdstat_disks *

Is there an example of setting this? Maybe with parent.configs.netdata parameter included with -f values.yaml when running helm install? What would values.yaml need to contain to deploy the required netdata.conf configuration?

I think I'm lacking an understanding of the configmap layout and need an example to configure Netdata properly.

[cheyngoodman]

I think the solution is to create a values.yaml file and deploy using:

CLAIM_TOKEN="<SECRET>"
helm repo add netdata https://netdata.github.io/helmchart
helm install netdata netdata/netdata \
--set parent.claiming.enabled="true" \
--set parent.claiming.token="$CLAIM_TOKEN" \
--set child.claiming.enabled="true" \
--set child.claiming.token="$CLAIM_TOKEN" \
-f values.yaml

# values.yaml
---
parent:
  configs:
    netdata:
      data: |-
        [global]
          hostname = netdata-parent
        [db]
          mode = dbengine
        [health]
            enabled alarms = !system_clock_sync_state !mdstat_disks *
        [plugins]
          cgroups = no
          tc = no
          enable running new plugins = no
          check for new plugins every = 72000
          python.d = no
          charts.d = no
          go.d = no
          node.d = no
          apps = no
          proc = no
          idlejitter = no
          diskspace = no