unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 40738@debbugs.gnu.org
Subject: [bug#40738] Prometheus (and Alertmanager)
Date: Mon, 20 Apr 2020 22:11:03 +0100	[thread overview]
Message-ID: <87v9lt50d4.fsf@cbaines.net> (raw)

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

I've had a go at packaging Prometheus and Alertmanager, as well as
writing Guix services for both of them.

The packages build, but still need quite a bit of work. They're both
written in Go, so the Git repositories not only include the relevant
source code, but the source code of the entire dependency tree (hence
the packages have no inputs). That'll need addressing.

I've tested the Prometheus service, and it seems to work, although there
isn't any record types for the Prometheus configuration yet. I haven't
yet tested the Alertmanager service and the system test doesn't pass, I
believe more configuration is required than Prometheus.

Having a Prometheus service would be a good complement for the existing
Prometheus Node exporter service in Guix.

I'll send the patches following this email.

Thanks,

Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

             reply	other threads:[~2020-04-20 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 21:11 Christopher Baines [this message]
2020-04-20 21:17 ` [bug#40738] [PATCH 1/4] gnu: Add prometheus Christopher Baines
2020-04-20 21:17   ` [bug#40738] [PATCH 2/4] services: Add a Prometheus service Christopher Baines
2020-04-20 21:17   ` [bug#40738] [PATCH 3/4] gnu: Add alertmanager Christopher Baines
2020-04-20 21:17   ` [bug#40738] [PATCH 4/4] services: Add a service for Alertmanager Christopher Baines
2020-05-03 10:56 ` [bug#40738] Prometheus (and Alertmanager) Ludovic Courtès
2020-05-03 11:17   ` Christopher Baines

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87v9lt50d4.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=40738@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).