From: Steve S. <ste...@gm...> - 2011-04-30 07:30:05
|
On Wed, Apr 6, 2011 at 17:56, Thomas Baumann <bt0...@gm...> wrote: > >From reading the mailing list and some howtos, that this feature is > planned but not complete available yet in munin 2.0. First, sorry about the delay. But, yup, that's the idea (to have it in 2.0) > RRDs::create ("$fname", "-s 60", Ouch, you have a *very* valid point. I completely forgot to address the RRD "step" in my commits about a flexible update_rate. That's has some nasty consequences, the most important is an eventual resolution loss. And I'm very sensitive to data loss, specially when it happens silently. > The cronjob was changed to 1 minute as well: > > */1 * * * * munin test -x /usr/bin/munin-cron && /usr/bin/munin-cron > > I tried to change the munin-graph as well, but I end up with graphs > showing nothing or some gaps. In 1.4, you can try to externalize munin-update from munin-cron. It might help to avoid missed data collections, since the whole update + graph + html + limits could take more than 1 min. Having munin-graph/html/limits running every 5 min is not that bad, since you'll still have a 1 min precision in the RRD. > Could somebody tell me, if this is the right way to do it. As > reference the changed munin-graph as well. You did the right thing. But the main prob is that 300 (5min) is hard coded a lot all throughout the code. I noticed that when trying, for 2.0, to have a parametric --step as you rightfully implied. -- Steve Schnepp http://blog.pwkf.org/ |