#11948 Request for communishift-metrics namespace
Closed: Fixed with Explanation 14 hours ago by kevin. Opened a month ago by bookwar.

Communishift namespace creation


Project Name: metrics

Project Administrators: bookwar

Requires Persistent Storage?: no

How much space do you need?: N/A

How is this project related to Fedora?


I'd like to setup a stateless Prometheus/Grafana/AlertManager/AlertManager-to-Matrix service, which can be used to measure the current activity in the project and send information messages to Matrix chats.

The intent is to cover personal or community driven use cases which are not (yet?) eligible to be covered by the "official" infrastructure monitoring and to give the tooling for some data analysis for folks who want to play with it.

Example:

With fm-metrics[1] service (which simply labels and counts messages it reads from the message bus) I can count certain type of messages in the Fedora Message bus and see the spikes in org.fedoraproject.tests.queued or org.fedoraproject.test.complete topics and send alerts to #fedora-ci Matrix channel.

I can also see the activity in the f40-updates tag, and so on.

There is not going to be any personal data in this, as it is going to be just a Prometheus metrics scraper with a configuration in GIt.

[1] https://github.com/bookwar/fm-metrics


By submitting this ticket you agree to you have read and understood
https://docs.fedoraproject.org/en-US/infra/communishift/#_service_usage_requirements


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: communishift, medium-gain, medium-trouble, ops

22 days ago

Metadata Update from @kevin:
- Issue assigned to kevin

14 hours ago

So sorry this one fell off our radar. ;(

Created. Let us know if you need any more resources or hit any problems.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

14 hours ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog