i forgot to add that the most complicated part in this might be to stay backward compatible with existing installations that symlink their plugins with just one parameter (the aspect)
varnish_ -> varnish_expunge instead of the new way (instance + aspect) varnish_ -> varnish_project1_expunge i don't have any idea on how to solve that atm.. :-( regards, fRiSi Am Montag, 14. Juni 2010, um 14:53:14 schrieb Harald Friessnegger: > This is a feature request for the munin plugin varnish_ > Although it's rather trivial to implement i'm not enough into perl to > contribute a patch. > > > We’re running multiple varnish instances (different varnishd/varnishstats > binaries) on our servers. > > Currently varnish_ only allows to monitor one of them. > (http://varnish-cache.org/browser/trunk/varnish-tools/munin/varnish_?rev=44 > 39) > > As a workaround i’m having something like varnish1_ varnish2_ scripts with > some modifications: > > line 759: $self =~ s/^.*\/varnish_//; > becomes > line 759: $self =~ s/^.*\/varnish1_//; > > and > line 731: print “graph_category Varnish\n”; > becomes > line 731: print “graph_category Varnish Project 1\n”; > > > Would be great if varnish_ was a wildcard plugin such as haproxy > (http://munin.projects.linpro.no/browser/trunk/plugins/node.d/haproxy_.in) > as the ending “_” already suggests. > > This way one needn’t copy/paste/modify varnish_ but simly use symlinks like > varnish_instance1_uptime and varnish_instance2_uptime > > > Thanks for your help/attention > fRiSi -- Webmeisterei GmbH - Büro für Netzfragen Tel: +43 5572 908877, Fax: +43 5572 908877-66 Steinebach 18, A-6850 Dornbirn http://www.webmeisterei.com _______________________________________________ varnish-misc mailing list [email protected] http://lists.varnish-cache.org/mailman/listinfo/varnish-misc
