Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Metrics and monitoring #5

Open
jlebon opened this issue Jul 9, 2019 · 1 comment
Open

Metrics and monitoring #5

jlebon opened this issue Jul 9, 2019 · 1 comment

Comments

@jlebon
Copy link
Member

jlebon commented Jul 9, 2019

We will soon have two services here: coreos-koji-tagger and config-bot. We need to figure out how we'll monitor these services and e.g. be alerted if they go down.

Right now coreos-koji-tagger is planned to run in the OpenShift infra. Would probably make things easier to implement if we just run config-bot there too.

See related discussions in #3 (comment).

/cc @lucab since he has experience in that area (and I think was looking at this for the Cincinnati server as well?)
@jlebon jlebon mentioned this issue Jul 9, 2019
Merged
@lucab
Copy link

lucab commented Jul 9, 2019

I think that coreos-koji-tagger, like the Cincinnati server, runs on Fedora infrastructure: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/openshift-apps/coreos-koji-tagger.yml

To my knowledge, that Openshift cluster does not (yet) have Prometheus+AlertManager, but monitoring is done via Nagios.

@jlebon jlebon mentioned this issue Dec 17, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lucab @jlebon