wombat.ch

Add also to

vi /etc/cron.d/munin-plugin-apt
03  * * * *    root    apt update > /dev/null 2>&1
18  * * * *    root    apt-get  update > /dev/null 2>&1
33  * * * *    root    apt upgrade > /dev/null 2>&1
48 * * * *    root    apt-get upgrade > /dev/null 2>&1

#   service cron reload

==============================================================
Problems:
:/etc/munin/plugins# munin-run apt
pending.value 3
pending.extinfo file libmagic-mgc libmagic1
hold.value 0
---
:/etc/munin/plugins# munin-run apt_all
pending_stable.value 0
hold_stable.value 0
pending_testing.value 0
hold_testing.value 0
pending_unstable.value 0
hold_unstable.value 0

Munin | Group Information


How to use and where to define Groups, and the difference in using the Munin-Master <--> Munin-Node vs. Munin-Master with SNMP

Munin-Master <--> Munin-Node

in the Munin-Master device in the file

#   /etc/munin/munin.conf

you have information like this to add for each Munin-Node

[munin-node.yourDomani.org]
    address 10.10.10.10
    use_node_name yes

With this ([munin-node.yourDomani.org]) part you are able to define some structure for your device.
The first part, bevor the dot, is your device you wish to monitore, behinde the dot you build your structure.

If you wish to Group it and split your VM, Switch, Hardware, Infrastructure device you could create a structure like this

[server1.HW]
[Munin.VM]
[debian9.VM-Test]

Munin-Master <--> SNMP-"Node"

in the Munin-Master device in the file

#   /etc/munin/munin.conf

you have information like this to add for each

[munin-node.yourDomani.org]
    address 10.10.10.10
    use_node_name yes