From: felix <felix@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] collectd: add write_prometheus plugin
Date: Thu, 01 Oct 2020 06:13:17 +0200 [thread overview]
Message-ID: <20201001041317.iy42PnruJoXPjLuzrxfkF9eY0OQXvYAHSAqG1qLmSGc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21202@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
There is an updated pull request by felix against master on the void-packages repository
https://github.com/felix/void-packages collectd
https://github.com/void-linux/void-packages/pull/21202
collectd: add write_prometheus plugin
A patch file from https://github.com/void-linux/void-packages/pull/21202.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-collectd-21202.patch --]
[-- Type: text/x-diff, Size: 2056 bytes --]
From 8e461a38b918d9e78d982f2425852bcb9fc369aa Mon Sep 17 00:00:00 2001
From: Felix Hanley <felix@userspace.com.au>
Date: Tue, 21 Apr 2020 22:53:05 +1000
Subject: [PATCH] collectd: add write_prometheus plugin
---
srcpkgs/collectd/template | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/collectd/template b/srcpkgs/collectd/template
index a88454aa4e8..88b2ace370e 100644
--- a/srcpkgs/collectd/template
+++ b/srcpkgs/collectd/template
@@ -6,13 +6,16 @@ build_style=gnu-configure
configure_args="$(vopt_enable rrdtool rrdtool) $(vopt_enable perl perl)
$(vopt_enable notify notify_desktop) --with-libiptc --enable-virt
--sysconfdir=/etc --disable-static --with-fp-layout=nothing
- --with-python=/bin/python3 --disable-werror"
+ --with-python=/bin/python3 --disable-werror
+ $(vopt_with prometheus "libmicrohttpd protobuf-c")
+ $(vopt_enable prometheus write_prometheus)"
conf_files="/etc/collectd.conf"
hostmakedepends="automake pkg-config libtool libltdl-devel glib-devel"
makedepends="libcurl-devel iptables-devel libressl-devel libsensors-devel
libesmtp-devel zlib-devel yajl-devel python3-devel libxml2-devel net-snmp-devel
libgcrypt-devel libmysqlclient-devel libltdl-devel libvirt-devel
- $(vopt_if notify libnotify-devel) $(vopt_if rrdtool rrdtool-devel)"
+ $(vopt_if notify libnotify-devel) $(vopt_if rrdtool rrdtool-devel)
+ $(vopt_if prometheus 'protobuf-c-devel libmicrohttpd-devel')"
short_desc="Daemon which collects system performance statistics periodically"
maintainer="Steve Prybylski <sa.prybylx@gmail.com>"
license="GPL-2.0-only, MIT"
@@ -21,8 +24,9 @@ distfiles="https://collectd.org/files/${pkgname}-${version}.tar.bz2"
checksum=37b10a806e34aa8570c1cafa6006c604796fae13cc2e1b3e630d33dcba9e5db2
LDFLAGS="-lgcrypt"
-build_options="rrdtool perl notify"
+build_options="rrdtool perl notify prometheus"
desc_option_rrdtool="Enable support for RRDTool"
+desc_option_prometheus="Enable write_prometheus plugin"
if [ -z "$CROSS_BUILD" ]; then
build_options_default="rrdtool perl"
next prev parent reply other threads:[~2020-10-01 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 12:53 [PR PATCH] " felix
2020-04-30 2:04 ` [PR PATCH] [Updated] " felix
2020-09-29 1:59 ` [PR REVIEW] " ericonr
2020-09-30 1:51 ` felix
2020-09-30 2:21 ` ericonr
2020-10-01 4:13 ` felix [this message]
2020-10-10 22:49 ` ericonr
2020-10-12 6:04 ` felix
2020-12-20 4:09 ` [PR PATCH] [Merged]: " ericonr
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=20201001041317.iy42PnruJoXPjLuzrxfkF9eY0OQXvYAHSAqG1qLmSGc@z \
--to=felix@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).