On 2020-06-24 10:50, Harry Wagstaff wrote:
Hi all,
I'm interested in using Prometheus with a project due to its nice
integration with gitlab, which my team uses extensively.
However, it seems that Prometheus is mainly intended for monitoring of
live services whereas we would be mainly wanting to use it to store
eg. Per-commit (or at least, regular) results of performance
regressions, code metrics, etc. (And so we would also extensively be
using pushgateway).
Does anyone have experience in using Prometheus in this kind of
arrangement? Are there more suitable tools available? Like I mentioned
Prometheus is particularly attractive due to gitlab integration.
Storing things per commit would need an event based storage system,
which Prometheus does not do. For that you are best looking at a more
general database (such as MySQL or InfluxDB).
Periodic checks are within the scope of Prometheus, so you could store
(for example) the code coverage level. It wouldn't be linked to commits
in any way.
To be honest, it is probably easier to add something to your build
pipelines to store that sort of data in a standard database (against
commit) rather than using Prometheus.
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/ba4f5f04f0964deaedf23b1b937dd966%40Jahingo.com.
