munin-monitoring / munin / 18387880490
46%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 20
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 46.253%. Remained the same
18387880490

push

github

web-flow 
df: add an example of name for the file (#1668)

I created a file with this config for the `df` plugin:

```
[df*]
env.warning 93
env.critical 98
```

I named it `/etc/munin/plugin-conf.d/df` and the settings were ignored.

Then I renamed it to `/etc/munin/plugin-conf.d/zz_df` and the settings
were applied.

It looks like my custom file must be read after
`/etc/munin/plugin-conf.d/munin-node`, so I used the `zz_` prefix.

I didn’t change the file `/etc/munin/plugin-conf.d/munin-node` to avoid
conflicts later when updating munin. It contains this configuration:

```
(…)
[df*]
env.warning 92
env.critical 98
env.exclude_re ^/run/user ^/var/lib/docker
(…)
```

### Test

```
# ls
df  dhcpd3  munin-node  README  spamstats
# munin-run --debug df
(…)
# Environment warning = 92
(…)
# mv -v df zz_df
renamed 'df' -> 'zz_df'
# munin-run --debug df
(…)
# Environment warning = 93
(…)
```

So yes the order of the files is important.

### Another proof

Files are processed by alphabetical order:

```
# munin-run --debug df
(…)
# Processing plugin configuration from /etc/munin/plugin-conf.d/README
# Processing plugin configuration from /etc/munin/plugin-conf.d/dhcpd3
# Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node
# Processing plugin configuration from /etc/munin/plugin-conf.d/spamstats
# Processing plugin configuration from /etc/munin/plugin-conf.d/zz_df
```

1043 of 2255 relevant lines covered (46.25%)

275.02 hits per line

Jobs
ID Job ID Ran Files Coverage
1 18387880490.1 20
46.25
 GitHub Action Run
Source Files on build 18387880490