[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #33972 [Internal Services/Tor Sysadmin Team]: Add Nagios check for CollecTor
#33972: Add Nagios check for CollecTor
-----------------------------------------------------+-----------------
Reporter: karsten | Owner: tpa
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
-----------------------------------------------------+-----------------
We currently have a metrics-specific Nagios host that we want to shut down
soon. One of its checks is to see whether CollecTor's files are becoming
unavailable or stale. This check is not easily transferable to Tor's
Nagios host, because it depends on a code base that is not being
maintained anymore and that we want to deploy on Tor's Nagios host. That's
why I rewrote this check in a simple Python script to be deployed on Tor's
Nagios instance.
Questions:
- anarcat and/or weasel: do you have any concerns about deploying this
check in Tor's Nagios host alongside the
[https://gitweb.torproject.org/admin/tor-nagios.git/tree/tor-nagios-
checks/checks/tor-check-onionoo Onionoo check]?
- irl: do you spot any checks in this Python script that are way off, or
other checks that are missing?
- atagar, other Python people: do you mind reviewing the Python code for
general code improvements? The goal is to have a single, self-contained,
easy-to-read Python script that produces just the data we need for Nagios
to send out alerts.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33972>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs