Hey all,
following up on this, we wrote a small prometheus-onion-exporter in go:
https://github.com/systemli/prometheus-onion-service-exporter
Maybe it helps you monitoring your onion sites.
cheers shadow
On 31.12.19 18:15, shadow wrote:
Thank you for your answers,
I will checkout the different solutions and see what fits for my usecase.
Alecs piece of software was a good first starting point for and shows that it is a complexer problem.
I hope you all are doing well and have a happy new year,
shadow
On 28.12.19 17:50, shadow wrote:
Dear fellow Onion Service operators,
I'm curios how you monitor the availability of your onion services?
I implemented a solution with icinga2 check commands. It basically queries the onion service via torsocks and check_tcp command [1].
object CheckCommand "check_tor_onion" { command = [ "torsocks", PluginDir + "/check_tcp" ] timeout = 6m arguments = { "-H" = "$hostname$" "-p" = "$port$" "-t" = "$timeout$" } }
This solution is kind of flaky and produces a lot of mail noise, even if I run it with large timeout value (360s), check attempts and retry intervals.
Recently I came across the tool called hsprober [2], which looks like a more compelling option. though it requires a prometheus setup.
Since it is a network, where connections constantly looses connections, I would like to know how you treat this flakyness. Regardless of which software stack you use, I'm interested in your concept for monitoring your onion services from the outside (user side) and from the inside (server side). And also which tools do you use.
Thank you for any answers and opinions. Have a happy new year.
shadow
[1] - https://www.monitoring-plugins.org/doc/man/check_tcp.html [2] - https://git.autistici.org/ale/hsprober
tor-onions mailing list tor-onions@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions
tor-onions mailing list tor-onions@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions