Ticket #14 (new enhancement)

Opened 7 years ago

Last modified 1 year ago

Wildcards in munin.conf

Reported by: jo Assigned to: janl
Priority: normal Milestone: Munin 3.0
Component: master Version:
Severity: normal Keywords:
Cc:

Description

It should be possible to use wildcards in munin.conf. E.g.

[hostname]

*.type LINE2

Change History

06/28/05 16:26:30 changed by anonymous

  • component changed from node to server.

07/12/05 13:14:04 changed by jo

  • severity changed from normal to enhancement.

11/06/05 14:03:31 changed by lupe

It should also be possible to wildcard the [hostname] to allow overrides for plugins on all hosts or a subset.

Also, consider using regexes, not wildcards.

12/02/05 12:24:15 changed by jo

Original sourceforge feature request: Wildcards in munin.conf would be nice. You can already do:

[fnord.linpro.no] address 127.0.0.1 cpu.system.warning 100

...but it would really be nice to do things like:

[fnord.linpro.no] df.*.warning 97

...and even nicer:

[*] cpu.system.warning 100

[Workstations;*] cpu.system.critical -1: # Disable on workstations

02/29/08 22:12:13 changed by jo

  • status changed from new to assigned.

10/20/09 23:42:34 changed by janl

  • owner changed from jo to janl.
  • status changed from assigned to new.
  • version deleted.

11/14/09 23:13:32 changed by janl

  • milestone changed from Munin 1.4 to Munin 1.5.

01/18/11 15:35:26 changed by jo

  • milestone changed from Munin 2.0 to Munin 3.0.

This won't make it into 2.0. Rescheduling for 3.0 (which might be optimistic, to be honest.)