Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duplicate metrics collected on trackers #4

Closed
notslang opened this issue Jan 27, 2018 · 12 comments
Closed

duplicate metrics collected on trackers #4

notslang opened this issue Jan 27, 2018 · 12 comments

Comments

@notslang
Copy link

I get this error:

An error has occurred during metrics collection:

96 error(s) occurred:
* collected metric transmission_torrent_downloads_total label:<name:"id" value:"155" > label:<name:"name" value:"dns-registration-2011-to-2016.csv.xz" > label:<name:"tracker" value:"udp://open.demonii.com:1337" > gauge:<value:-1 >  was collected before with the same name and label values
* collected metric transmission_torrent_leechers label:<name:"id" value:"155" > label:<name:"name" value:"dns-registration-2011-to-2016.csv.xz" > label:<name:"tracker" value:"udp://open.demonii.com:1337" > gauge:<value:-1 >  was collected before with the same name and label values
* collected metric transmission_torrent_seeders label:<name:"id" value:"155" > label:<name:"name" value:"dns-registration-2011-to-2016.csv.xz" > label:<name:"tracker" value:"udp://open.demonii.com:1337" > gauge:<value:-1 >  was collected before with the same name and label values
...

Which seems to be caused by duplicate trackers on torrents. If I do a request on the RPC then it shows that there actually are duplicate trackers on the torrent and transmission doesn't deduplicate or ignore them.

@metalmatze
Copy link
Owner

Hmm. I guess we should include a label with the tracker then. Would you like to create a PR? ☺️

@pedrojimenez
Copy link

Same problem here ...
@metalmatze have you tested this commit ? are you merging it ?

Regards

@jonnrb
Copy link

jonnrb commented Apr 9, 2018

FWIW I tested this with a torrent that caused this issue it no longer crashed...

@metalmatze
Copy link
Owner

Sorry. Looking into it.

I have the feeling that it still needs an additional label. Is there a torrent, e.g. some linux distro, which has multiple trackers, so I can test this somehow?
Thanks!

@pedrojimenez
Copy link

pedrojimenez commented Apr 10, 2018

Currently on master with this torrent:

* collected metric transmission_torrent_downloads_total label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:-1 >  was collected before with the same name and label values
* collected metric transmission_torrent_leechers label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:2 >  was collected before with the same name and label values
* collected metric transmission_torrent_seeders label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:305 >  was collected before with the same name and label values
* collected metric transmission_torrent_downloads_total label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:-1 >  was collected before with the same name and label values
* collected metric transmission_torrent_leechers label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:2 >  was collected before with the same name and label values
* collected metric transmission_torrent_seeders label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://tracker.opentrackr.org:1337" > gauge:<value:305 >  was collected before with the same name and label values
* collected metric transmission_torrent_downloads_total label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://9.rarbg.com:2750" > gauge:<value:-1 >  was collected before with the same name and label values
* collected metric transmission_torrent_leechers label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://9.rarbg.com:2750" > gauge:<value:2 >  was collected before with the same name and label values
* collected metric transmission_torrent_seeders label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://9.rarbg.com:2750" > gauge:<value:221 >  was collected before with the same name and label values

@pedrojimenez
Copy link

Any news on this ?

@metalmatze
Copy link
Owner

Not really from my side. I guess I'd need to take another look.

metalmatze added a commit that referenced this issue Oct 11, 2018
Deduplicate trackers, fixes #4
@metalmatze
Copy link
Owner

I have merged the PR and will do some more testing in the next days.

@pedrojimenez
Copy link

Thanks @metalmatze ...
I have just tested it with same source transmission and updated exporter from master ... Same results:

* collected metric transmission_torrent_leechers label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://9.rarbg.com:2750" > gauge:<value:0 >  was collected before with the same name and label values

* collected metric transmission_torrent_seeders label:<name:"id" value:"13" > label:<name:"name" value:"pwned-passwords-2.0.txt.7z" > label:<name:"tracker" value:"udp://9.rarbg.com:2750" > gauge:<value:124 >  was collected before with the same name and label values

@pedrojimenez
Copy link

Any news ?

@metalmatze
Copy link
Owner

No news. Can you try to reproduce and send some instructions on how to do it? Maybe you might also want to create a PR? I don't have anything running into that problem myself at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants