From sunku.ranganath at intel.com  Wed Sep  4 00:15:51 2019
From: sunku.ranganath at intel.com (Ranganath, Sunku)
Date: Tue, 3 Sep 2019 22:15:51 +0000
Subject: [collectd] preparations for collectd-5.10
In-Reply-To: <20190821064933.GA9570@hilbert.berg.ol>
References: <20190821064933.GA9570@hilbert.berg.ol>
Message-ID: <E9F2D0F6562EE141BE3F92E1EFFDD921F1D04A30@ORSMSX121.amr.corp.intel.com>

Thanks Matthias for initiating the required process for Collectd 5.10.
Appreciate your time in taking charge of release process, although we are a bit late as compared to our original date of releasing 5.10 by August timeframe. Better late than never!

In order to reduce the burden to one person and have some predictability in the community, 
I would ask the community to take a look at the Collectd Release Process Proposal document detailed at [1].

This would allow us to remove any roadblocks and establish few guidelines. Please feel free to comment on the document.

[1] https://docs.google.com/document/d/1Ha9zPyKa_1pBar58LUPRf4EV2ap1sMcrOtRz3qauogo/edit 


Thanks,
Sunku Ranganath

-----Original Message-----
From: collectd [mailto:collectd-bounces at verplant.org] On Behalf Of Matthias Runge
Sent: Tuesday, August 20, 2019 11:50 PM
To: collectd at verplant.org
Subject: [collectd] preparations for collectd-5.10

Hi,

back in February, when we had our face to face meeting, we agreed on getting back to three releases per year, one in April, one in August, and one in December.

5.9 was a bit delayed, but I would like to get back to the cycle.

That means: I'm proposing 5.10 to be released in September, and I would also like to see a code-freeze/feature freeze.

Detailed, that'd mean:

  - Sept 16: feature freeze/code freeze; only bug fixes allowed.
  - Sept 30: 5.10 release.

Meanwhile, I would also like to see a 5.9.2 release to fix the issues[1].

Matthias


[1] https://github.com/collectd/collectd/issues?q=is%3Aissue+milestone%3A5.9.2
--
Matthias Runge <mrunge at matthias-runge.de>

_______________________________________________
collectd mailing list
collectd at verplant.org
https://mailman.verplant.org/listinfo/collectd

From gpanoutsak at gmail.com  Fri Sep 27 15:40:55 2019
From: gpanoutsak at gmail.com (Georgia Panoutsakopoulou)
Date: Fri, 27 Sep 2019 16:40:55 +0300
Subject: [collectd] Unsuccessful use of dpdkstat plugin
Message-ID: <CAG2+9UFaKAH-kVcCKmxBKw5mJMiCfhDNWbaGH67J-tHKq=d7XQ@mail.gmail.com>

Hello,

We have been trying to use the dpdkstat plugin on collectd without success.

Although it seems to be enabled, no dpdkstats metrics are reported with the
LISTVAL request of the plain text protocol.



We have followed the instructions at
https://buildmedia.readthedocs.org/media/pdf/opnfv-barometer/stable-gambia/opnfv-barometer.pdf
(in “DPDK plugins” section), and at
https://github.com/collectd/collectd/blob/master/docs/BUILD.dpdkstat.md.



In the logs we can see that the dpdkstat plugin has been successfully
loaded.



Is there anything that we may be missing? Should we have a DPDK app
actively using the DPDK-bound interfaces for stats to be listed?


An excerpt from the logfile is attached.

Thank you,

Georgia Panoutsakopoulou
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20190927/046a59dc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: collectd.log
Type: application/octet-stream
Size: 18015 bytes
Desc: not available
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20190927/046a59dc/attachment-0001.obj>

From manoj.srivastava.1962 at gmail.com  Mon Sep 30 21:03:42 2019
From: manoj.srivastava.1962 at gmail.com (Manoj Srivastava)
Date: Mon, 30 Sep 2019 12:03:42 -0700
Subject: [collectd] [Feature Request/Version 6.0]: Adding Labels to
 Collectd Metrics #3094
Message-ID: <CABkpOEVuE9Czg0S95FZOPvY8VqjvNvra5CsjFi3No4a1+GcBgA@mail.gmail.com>

Hi,

    I have an initial stalking horse commit based on the 5.9 branch that
implements the data structures in the design docs, and has unit tests to
the avl tree used in the structures. I think we need some discussion on how
to convert the current value_list_t 5-tupples --> name + labels structure
in the new format. Also, how should we deal with metadata lists in the new
format?

  I'll try and put together the design thoughts in a document and share
that around, and perhaps a code snippet or two t go along with it.

   Manoj

New basic data structures and start of branch:
https://github.com/srivasta/collectd/tree/metric-label-support

Adding Labels to Collectd Metrics
https://docs.google.com/document/d/173gGP3tUD3yfN2NNHxCv0BsKsacfDlSyoaQIn7MqLtQ/edit?usp=sharing
Compare data structures for metric labels (collectd)
https://docs.google.com/document/d/1RZ7YAO6lWcDDvevzxFGVDgv4UQpdgWoT7OCP9Vpb2CU/edit?usp=sharing
-- 
The Basis of the Universe Isn’t Matter or Energy—It’s Data
Manoj Srivastava <srivasta at golden-gryphon.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20190930/754f4270/attachment.html>