[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #31159 [Internal Services/Tor Sysadmin Team]: Monitor anti-censorship www services with prometheus
#31159: Monitor anti-censorship www services with prometheus
-------------------------------------------------+---------------------
Reporter: phw | Owner: tpa
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #30152 | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+---------------------
Comment (by phw):
Replying to [comment:1 hiro]:
> There is also another aspect to consider, in the case of a service like
gettor, monitoring the https endpoint will only give us some info about
the static html we are serving with apache. Gettor itself (the service
sending emails) is a twisted service instead.
[[br]]
Gotcha. We have a similar problem with BridgeDB because it is exposed over
an Apache reverse proxy and you cannot directly talk to BridgeDB.
However, if BridgeDB is down, bridges.torproject.org responds with an
internal server error if I remember correctly, so we can still monitor
BridgeDB despite the reverse proxy, right?
To monitor BridgeDB, we need to set up an exporter, right?
[[br]]
> Maybe we can consider an approach in which services expose an http
endpoint that we can use to know that the service is alive. Otherwise I
think we could do some other monitoring via nagios checks.
[[br]]
I think we already have that for BridgeDB and snowflake's website but not
for GetTor.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31159#comment:2>
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