public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] New category: app-metrics
Date: Tue, 20 Mar 2018 06:21:00 +0100	[thread overview]
Message-ID: <7e36a181-afe0-1b4f-1ee3-436afeb79805@gentoo.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]

Hi everyone,

I'm planning to add a new category app-metrics, which is mainly (at
least for my own use case) going to be used for prometheus[0] and its
exporters providing endpoints for prometheus. It can be used for other
packages whose _main_ purpose is to provide metrics, transform or
consume them.

* net-analyzer/prometheus
* app-admin/bind_exporter
* app-admin/elasticsearch_exporter
* app-admin/mongodb_exporter
* app-admin/nginx-vts-exporter
* app-admin/prom2json
* dev-util/buildbot-prometheus

In addition, the following packages will drop their prometheus- prefix
during the package move:

* net-analyzer/prometheus-blackbox_exporter
* net-analyzer/prometheus-node_exporter
* net-analyzer/prometheus-redis_exporter
* net-analyzer/prometheus-snmp_exporter
* net-analyzer/prometheus-uwsgi_exporter
* net-analyzer/prometheus-pushgateway
* net-analyzer/prometheus-alertmanager

With the growing adoption of prometheus I expect more exporters to be
added (I have five more that I want to add in the near future).


Thanks,

Manuel

[0] https://prometheus.io



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 632 bytes --]

             reply	other threads:[~2018-03-21 23:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  5:21 Manuel Rüger [this message]
2018-03-22  8:21 ` [gentoo-dev] New category: app-metrics Fabian Groffen
2018-03-22  8:57 ` Dirkjan Ochtman
2018-03-26 16:51   ` Thomas Deutschmann

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=7e36a181-afe0-1b4f-1ee3-436afeb79805@gentoo.org \
    --to=mrueg@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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