monit-configuration issueshttps://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues2022-03-01T17:56:58Zhttps://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/6Add "end-to-end" test that talks to moat2022-03-01T17:56:58ZPhilipp Winterphw@torproject.orgAdd "end-to-end" test that talks to moatTo catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then...To catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then try to talk to moat and return with exit code 0 if this succeeded.
The challenge is that we should use the same tor and obfs4proxy version as Tor Browser does. And even then, there is no guarantee that we're catching all possible problems – for example, an issue may be limited to Windows. Still, having a test like this would probably go a long way.
(We discussed this topic in [today's anti-censorship meeting](http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-12-17-15.57.html)).https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/5Monitor meek bridge's usage numbers and alert if it falls below threshold2021-06-10T14:12:56ZPhilipp Winterphw@torproject.orgMonitor meek bridge's usage numbers and alert if it falls below thresholdTo make sure that we catch problems like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we should put a system in place that monitors the usage numbers of our [meek bridge](https://metrics.torproject.org/rs.html#de...To make sure that we catch problems like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we should put a system in place that monitors the usage numbers of our [meek bridge](https://metrics.torproject.org/rs.html#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84DAE8) and alerts us if the numbers fall below a given threshold.
Here's what obfs4proxy's recent public key pinning issue looked like on our meek bridge:
![image](/uploads/449f3698b2c13eaf1461d10fcfe2496c/image.png)
We could regularly fetch the bridge's extrainfo descriptors and extract its usage numbers but there may be a better way to go about this.https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/2Add Snowflake's probe service once it's deployed2020-11-09T16:46:44ZPhilipp Winterphw@torproject.orgAdd Snowflake's probe service once it's deployedOver at tpo/anti-censorship/pluggable-transports/snowflake#40013, we are planning to build a probe service that helps Snowflake proxies figure out their NAT type. Once the service is live, we should start monitoring it.Over at tpo/anti-censorship/pluggable-transports/snowflake#40013, we are planning to build a probe service that helps Snowflake proxies figure out their NAT type. Once the service is live, we should start monitoring it.Philipp Winterphw@torproject.orgPhilipp Winterphw@torproject.org