[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #13003 [Onionoo]: Figure out a better strategy to avoid concurrent Onionoo executions

#13003: Figure out a better strategy to avoid concurrent Onionoo executions
-------------------------+-----------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------

Comment (by iwakeh):

 Yes, you're right. Monitoring should be separated from the application.

 For the front-end I'd suggest jmx/MBeans (actually
 [https://trac.torproject.org/projects/tor/ticket/11573#comment:9 comment
 here  #11573]). These can be very easily be verified with a nagios plugin.
 We even could re-use the jmx-example that comes with the tomcat-extra
 (i.e. jmx) package.
 It lists sessions, memory and the like as plain text.

 Using nagios plugins right now is useful and won't prevent any
 other/additional monitoring later on.
 And, python plugins are way quicker to write and deploy.

 Depending on the server setup, the nagios plugin might get read access to
 the logs of onionoo's backend?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13003#comment:20>
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