Ticket #51 (closed enhancement: fixed)

Opened 6 years ago

Last modified 3 months ago

node-side data cache (?)

Reported by: anonymous Assigned to: snide
Priority: normal Milestone: Munin 2.0
Component: design Version:
Severity: normal Keywords:
Cc: alt-j@users.sourceforge.net

Description

When network is not available munin do not gather data from nodes inserting empty values in graphs it would be nice if munin-node could gather results even while being offline and send them to munin when network is available

Change History

12/02/05 12:32:21 changed by alt-j at users.sourceforge.net

  • cc set to alt-j@users.sourceforge.net.

I'd like to second this request. I've considered switching to ORCA for this reason (they store all data on the client side which is rsync'd to the server for rrd and graph generation)...but munin is so much easier to configure :-)

12/02/05 12:35:33 changed by janl

  • severity changed from normal to enhancement.

This would require us to schedule sampling on the client. The client scheduling sampling _could_ increase scalability in number of nodes and plugins quite a lot. Should be a part of a scheduling/scalability redesign?

12/02/05 20:41:30 changed by janl

  • owner changed from jo to janl.
  • reporter changed from janl to anonymous.
  • milestone set to Munin 1.6.

06/15/06 20:18:18 changed by janl

  • milestone changed from Munin 1.6 to Munin 1.4.

This will be in 1.4

Nicolai

06/15/06 20:18:26 changed by janl

  • status changed from new to assigned.

08/30/06 02:15:39 changed by janl

  • component changed from node to design.

03/02/08 22:18:53 changed by janl

  • status changed from assigned to new.

Oh, btw, I have a node scheduler prototype if anyone else decides to start on this.

10/20/09 17:31:46 changed by janl

  • milestone changed from Munin 1.4 to Munin 1.5.

10/21/09 02:49:56 changed by janl

  • version deleted.

Won't make it into 1.4 due to time constraints.

01/18/10 13:06:58 changed by janl

  • owner changed from janl to snide.

Would fit into the objectives of 1.5, but not strictly needed. Feel free to ignore/push forward.

02/14/10 16:39:01 changed by snide

  • milestone changed from Munin 1.5 to Munin 1.6.

Client-side scheduling is quite intrusive, and is quite 1.6-grade feature (possibly even 2.0-grade)

05/13/11 21:33:22 changed by Tenzer

Isn't this feature more or less covered with munin-async-(client|server)?

09/12/11 15:34:46 changed by snide

  • status changed from new to closed.
  • resolution set to fixed.
  • milestone changed from Munin 3.0 to Munin 2.0.

In trunk:

- A plugin can send vector timed data. - there is munin-async