MUNIN-N...NFIGURE(1p)

📦
version 2.0.76 · 6 versions
, in ubuntu resolute, ubuntu stonking

✨ NAME ✨

munin-node-configure — bestie, this is the lil tool that lets you see and change which plugins are enabled. That's it, that's the vibe 💅

🌸 SYNOPSIS 🌸

munin-node-configure [options]

🦋 DESCRIPTION 🦋

So munin-node-configure reports which plugins are enabled on the current node, and it also suggests changes to that list. Like a lil plugin stylist fr fr.

By default this program just shows which plugins are activated on the system. Nothing extra, just receipts 👑

If you specify --suggest, it will present a table of plugins that will probably work (according to the plugins' autoconf command). Fingers crossed energy 🤞

If you specify --snmp, followed by a list of hosts, it will present a table of SNMP plugins that they support. Very demure, very networky 🧚

If you additionally specify --shell, shell commands to install those same plugins will be printed. These can be reviewed or piped directly into a shell to install the plugins. ⚠️ Piped directly into a shell, bestie. Review first, trust me.

💜 OPTIONS 💜

  • --help — Show this help page. Classic.
  • --version — Show version information.
  • --debug — Print debug information on the operations of munin-node-configure. This can be very verbose 😭. All debugging output is printed to STDOUT, and each line is prefixed with #. Only errors are printed to STDERR. So STDOUT is the yapper, STDERR is the one with something to say.
  • --pidebug — Plugin debug. Sets the environment variable MUNIN_DEBUG to 1 so that plugins may enable debugging. It's giving "tell the plugins to spill the tea" 🫖
  • --config <file> — Override configuration file [/etc/munin/munin-node.conf]
  • --servicedir <dir> — Override plugin directory [/etc/munin/plugins/]
  • --sconfdir <dir> — Override plugin configuration directory [/etc/munin/plugin-conf.d/]
  • --libdir <dir> — Override plugin library [/usr/share/munin/plugins/]
  • --suggest — Suggest plugins that might be added or removed, instead of those that are currently enabled. Main character behavior 💫

🌈 OUTPUT OPTIONS 🌈

By default, munin-node-configure will print out a table summarising the results. Cute, readable, iconic.

  • --shell — Instead of a table, print shell commands to install the new plugin suggestions. This implies --suggest, unless --snmp was also enabled. By default, it will not attempt to remove any plugins. Very "no takebacks" of it.
  • --remove-also — When --shell is enabled, also provide commands to remove plugins that are no longer applicable from the service directory. Now we're doing spring cleaning 🧹

🎀 PLUGIN SELECTION OPTIONS 🎀

  • --families <family,...> — Override the list of families that will be used (auto, manual, contrib, snmpauto). Multiple families can be specified as a comma-separated list, by repeating the --families option, or as a combination of the two. Mix and match, we love options 💖

When listing installed plugins, the default families are auto, manual and contrib. Only auto plugins are checked for suggestions. SNMP probing is only performed on snmpauto plugins. So like, each family has its own lane, respect the lane.

  • --newer <version> — Only consider plugins added to the Munin core since <version>. This option is useful when upgrading, since it can prevent plugins that have been manually removed from being reinstalled. This only applies to plugins in the auto family. It's literally the "don't bring back what I already said goodbye to" button 🚫

🦋 SNMP Options 🦋

  • --snmp <host|cidr,...> — Probe the SNMP agents on the host or CIDR network (e.g. 192.168.1.0/24), to see what plugins they support. This may take some time, especially if the many hosts are specified. ⏳ Like, go make a snack.

This option can be specified multiple times, or as a comma-separated list, to include more than one host/CIDR.

  • --snmpversion <ver> — The SNMP version (1, 2c or 3) to use. [2c]
  • --snmpport <port> — The SNMP port to use [161]
  • --snmpdomain <domain> — The Transport Domain to use for exchanging SNMP messages. The default is UDP/IPv4. Possible values: udp, udp4, udp/ipv4; udp6, udp/ipv6; tcp, tcp4, tcp/ipv4; tcp6, tcp/ipv6.

🔥 SNMP 1/2c authentication 🔥

SNMP versions 1 and 2c use a "community string" for authentication. This is a shared password, sent in plaintext over the network. 🚨 PLAINTEXT, bestie. On the network. Anyone with a packet sniffer is reading your mail.

  • --snmpcommunity <string> — The community string for version 1 and 2c agents. [public] (If this works your device is probably very insecure and needs a security checkup). 💀 Not the compliment you think it is.

💅 SNMP 3 authentication 💅

SNMP v3 has three security levels. Lowest is noAuthNoPriv, which provides neither authentication nor encryption. If a username and authpassword are given it goes up to authNoPriv, and the connection is authenticated. If privpassword is also given the security level becomes authPriv, and the connection is authenticated and encrypted. Glow up progression ✨

Note: Encryption can slow down slow or heavily loaded network devices. For most uses authNoPriv will be secure enough -- the password is sent over the network encrypted in any case.

ContextEngineIDs are not (yet) supported. Soon™, maybe, who knows.

For further reading on SNMP v3 security models please consult RFC3414 and the documentation for Net::SNMP. Homework, but make it network security 📚

  • --snmpusername <name> — Username. There is no default.
  • --snmpauthpass <password> — Authentication password. Optional when encryption is also enabled, in which case defaults to the privacy password (--snmpprivpass).
  • --snmpauthproto <protocol> — Authentication protocol. One of md5 or sha (HMAC-MD5-96, RFC1321 and SHA-1/HMAC-SHA-96, NIST FIPS PIB 180, RFC2264). [md5]
  • --snmpprivpass <password> — Privacy password to enable encryption. There is no default. An empty ('') password is considered as no password and will not enable encryption.

Privacy requires a privprotocol as well as an authprotocol and a authpassword, but all of these are defaulted (to des, md5, and the privpassword value, respectively) and may therefore be left unspecified.

  • --snmpprivproto <protocol> — If the privpassword is set this setting controls what kind of encryption is used to achieve privacy in the session. Only the very weak des encryption method is supported officially. [des]

munin-node-configure also supports 3des (CBC-3DES-EDE, aka Triple-DES, NIST FIPS 46-3) as specified in IETF draft-reeder-snmpv3-usm-3desede. Whether or not this works with any particular device, we do not know. 🤷‍♀️ Genuinely. Nobody knows. It's a mystery.

🌸 FILES 🌸

The lil cast of characters:

  • /etc/munin/munin-node.conf
  • /etc/munin/plugin-conf.d/*
  • /etc/munin/plugins/*
  • /usr/share/munin/plugins/plugins.history
  • /usr/share/munin/plugins/*

⭐ VERSION ⭐

This is munin-node-configure (munin-node) v2.0.76. Periodt.

🫶 AUTHORS 🫶

Jimmy Olsen, Nicolai Langfeldt, Matthew Boyle — the icons, the legends 👑

Copyright (C) 2003-2006 Jimmy Olsen, Nicolai Langfeldt.

Copyright (C) 2009-2010 Matthew Boyle

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

This program is released under the GNU General Public License.

And that's the whole page, bestie 🎀 This lil writeup rides along with perl v5.40.1, dated 2025-05-20, and it's the MUNIN-N...NFIGURE(1p) — a User Contributed Perl Documentation page. Go configure some nodes, you got this 💜
📦 where this page comes from