Re: [tor-relays] tor prometheus metrics -> expected label value, got "INVALID"
Hej David, Thanks for reporting and investigating!! :) Thank you for fixing and implementing in the first place! Really looking forward to see some nice graphs showing how many people use our services via onion. BTW: Implementation of nusenu feature request[1] for exposing more relay health metrics for prometheus would be awesome! :) Best, fran [1] https://gitlab.torproject.org/tpo/core/tor/-/issues/40194 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor prometheus metrics -> expected label value, got "INVALID"
On 23 Jan (11:36:05), Fran via tor-relays wrote:
> Hej,
>
> taking another look and comparing it to onion_services exporter there is a
> slight difference in the metrics output.
>
> prometheus-onion-service-exporter:
>
> onion_service_up{address="foobar:587",name="mail_v3_587",type="tcp"} 1
>
> vs output from tor:
>
> tor_hs_app_write_bytes_total{onion=foobar,port=80} 298891
Ah wow... you are indeed right.
I had problems recently with an exporter I made for something unrelated that
was not exporting labels as quoted strings...
I have opened a ticket:
https://gitlab.torproject.org/tpo/core/tor/-/issues/40552
Thanks for reporting and investigating!! :)
Cheers!
David
--
3obTrBY9FLhQsK4/YufSTiyO7ERRvmLFjMaVvocpZfQ=
signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Outdated GeoIP DB
We run the update command daily and sync the data from it. See: https://man-pages.ipfire.org/libloc/location.html As far as I understand this should update the local DB. Are we overlooking something? location version Mon, 24 Jan 2022 06:02:28 GMT location lookup 89.58.17.76 89.58.17.76: Network : 89.58.16.0/22 Country : Germany Autonomous System : AS197540 - netcup GmbH According to the ipfire devs the webservice at https://location.ipfire.org/lookup/89.58.17.76 does not update the db daily, since it uses the db version when the service started. So if you are using a daily updated version everything should fine on your side. The remaining questions (why does it believe it is DE vs AT) is a question for the ipfire devs. @Martin: I can recommend their mailing list: https://lists.ipfire.org/mailman/listinfo/location kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Outdated GeoIP DB
On 21/1/22 12:15, Valters Jansons wrote: > On Fri, Jan 21, 2022 at 1:05 PM Georg Koppen wrote: >> Yes, we realized that the GeoIP db needs an update again[1]. However >> there is currently no newer version available[2] it seems. :( > The issue is not the version of libloc. The problem resides in an > outdated local database. The library and binaries are not the same > project/build as the database project[1], which gets updated daily. > The database is not being updated for Tor. > > If you check the current lookup for the mentioned IP[2], it results in: > - Network: 89.58.16.0/22 > - Announced by: AS197540 - netcup GmbH > - Country: Austria > This seems to be correct, like Martin said it should be. > > [1] https://git.ipfire.org/?p=location/location-database.git;a=summary > [2] https://location.ipfire.org/lookup/89.58.17.76 Hey Valters, We run the update command daily and sync the data from it. See: https://man-pages.ipfire.org/libloc/location.html As far as I understand this should update the local DB. Are we overlooking something? Cheers, -hiro > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
