public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Collectd needs to be updated
Date: Sat, 08 Jan 2022 11:21:53 +0000	[thread overview]
Message-ID: <5C4F6DD3-6AE4-44F3-A833-82E316B68B9A@ipfire.org> (raw)
In-Reply-To: <8c1dc3db-40ef-673e-afa2-bf67b85847e9@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]

Hello,

> On 8 Jan 2022, at 11:19, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello development folks,
> 
> by coincidence, I stumbled across Collectd today.
> 
> Currently, we ship version 4.10.9 of it, released 2013-04-08. The latest release, however,
> is 5.12.0 (2020-09-03, as displayed in https://collectd.org/files/), while https://collectd.org/news.shtml
> still mentions 5.8.0 (2017-11-21) as the latest one.
> 
> Either way, we are lacking updates here. :-)

Not really. The format of the RRD databases has been changed in version 5 which is the reason why we are still on version 4.

There are a couple of conversations about this on this list which should point out what work has to be done to migrate. It will be at least:

* Updating collectd
* Export all RRD databases (potentially convert the data) and then create databases of the new format
* Update the code that generates the graphs to reflect the changed format

I always considered this a major task which isn’t worth the work.

-Michael

> Does anyone have some spare time for Collectd left, and is willing to work on this?
> 
> Thanks in advance, and best regards,
> Peter Müller


      reply	other threads:[~2022-01-08 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 11:19 Peter Müller
2022-01-08 11:21 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5C4F6DD3-6AE4-44F3-A833-82E316B68B9A@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox