bug#43239: [PATCH] gnu: Add guile-prometheus.

[Christopher Baines <mail@cbaines.net>]

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


Mathieu Othacehe <othacehe@gnu.org> writes:

> Hello Christopher,
>
>> +    (name "guile-prometheus")
>> +    (version (string-append "0-" revision "." (string-take commit 7)))
>
> I think that the usual pattern is something like:
>
> --8<---------------cut here---------------start------------->8---
>       (version (git-version "0.0.1" revision commit))
> --8<---------------cut here---------------end--------------->8---

Ah, yeah, I copied from a package definition not using that.

>> +    (inputs
>> +     `(("guile" ,guile-3.0)))
>> +    (home-page "https://git.cbaines.net/guile/prometheus")
>
> The linter reports that this URL is not reachable.

I think it's actually the source URL (with the /git bit in it ) that it
complains about:

gnu/packages/guile-xyz.scm:862:12: guile-prometheus@0-0.cbc6e1b: URI https://git.cbaines.net/git/guile/prometheus not reachable: 404 ("Not Found")

While the home page URL definitely works, that URL does 404, however it
seems to work just fine for cloning the repository, so I'm not quite
sure what if anything to do with this lint warning.

>> +    (synopsis "Prometheus client library for Guile")
>> +    (description
>> +     "This Guile library provides instrumentation code intended to be used
>> +with the Prometheus time series service.  Counter, gauge and histogram metric
>> +types are supported.")
>> +    (license license:gpl3+))))
>
> Otherwise, looks fine! Turns out I'm currently working on adding some
> metrics to Cuirass[1]. With commit 154232b, we should be able to add the
> two metrics proposed in the bug report. The next step is to actually
> compute, save and display those metrics.
>
> I'm just discovering this prometheus but may it could be a good
> candidate? Do you happen to have a server running prometheus?

I've with the version change, I've gone ahead and pushed. Thanks for
taking a look!

As for Cuirass metrics, that sounds exciting. I do happen to have a
Prometheus instance [1] which I've been using to monitor machines and
the Guix Build Coordinator that I run for the guix.cbaines.net build
farm.

1: http://mago.cbaines.net:9090/

While Prometheus can generate graphs, I've been using Grafana [2] to
build dashboards to visualise the Prometheus data.

2: http://mago.cbaines.net:3000/

This [4] is the dashboard I have for the guix.cbaines.net stuff, which
pulls together data from the node exporter service on the various
machines as well as the Guix Build Coordinator coordinator service
itself [5].

4: http://mago.cbaines.net:3000/d/gMq2pj3Wk/guix-cbaines-net
5: https://coordinator.guix.cbaines.net/metrics

Today, I've just started getting the Guix Data Service to export some
metrics [6] as I want to try and understand how the size of different
tables and indexes in the database change over time. There's a Grafana
dashboard for that too [7].

6: https://data.guix-patches.cbaines.net/metrics
7: http://mago.cbaines.net:3000/d/w7YijfvGz/guix-data-service

Additionally, I'm also running Alertmanager [8] which can send out
emails, for example when a machine is low on disk space.

8: http://mago.cbaines.net:9093/

Anyway, if you decide to have Cuirass export metrics in the Prometheus
style, just let me know and I can get the Prometheus instance I'm
running to scrape them. I can also give you access to Grafana so you can
create dashboards.

Thanks again,

Chris

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