Investigate New System Monitoring Methods #732
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#732
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Nagios isn't the best, it's fragile, and Nagios 3 won't do anything to change it.
There are other packages (Zabbix and Zenoss look good) out there, so we should look at these instead of rewriting the nagios configs for nagios3 and finding out it's still as ugly :).
I'm acquired publictest3.fp.o so we can test these packages, but we should work out exactly what our requirements are, as such we'll use the last half hour of the Infrastructure Meeting to discuss.
I've used Zabbix quite extensively at $DAYJOB and like it quite a bit. It's already in Fedora too. What I like the best is that it combines graphing and monitoring/notification all into one package. Unfortunately I won't be able to be at the meeting this Thursday...
I also support migrating to Zabbix. I've also used it at $dayjob and think it offers some excellent features. I'd be happy to help set it up and get it configured.
Short discussion was held, summary/logs are at: https://www.redhat.com/archives/fedora-infrastructure-list/2008-July/msg00143.html
We've not deployed zabbix completely but we have picked it and it is installed and running. Closing this ticket.