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

Download/upload by torrent #38

Open
daviddanko opened this issue Mar 4, 2024 · 2 comments
Open

Download/upload by torrent #38

daviddanko opened this issue Mar 4, 2024 · 2 comments

Comments

@daviddanko
Copy link

Hello,

Is there a way to show speeds by torrents? I am using the below exporter for qbittorrent but I like your project more. However, I would really like to have this on my grafana dashboard.

https://github.com/caseyscarborough/qbittorrent-grafana-dashboard

@taw123
Copy link

taw123 commented Mar 22, 2024

Actually I just installed a more efficient fork of Casey's original exporter you mentioned above. Vince's fork fixed a couple issue and brought the memory footprint down a bit https://github.com/vincejv/qbittorrent-exporter

If you go with that one, you can use Casey's dashboard which then gives you what you are looking for. I took the posted sample code for his "modern" dashboard then migrated it off Angular to Grafana's new(er) plugins. Pretty simple and works well. Still have some personal tweaking to do to suite my personal preferences (and colorblind eyesight) lol

Ideally I haven't gone through all their code to document what metrics THEY export and then see if I could just "borrow some of the dashboard components I like from this exporter's dashboard, grafting them onto the exported metrics Vince already provides. From a quick scan of how it's implemented I think he is grabbing almost everything from the WebUI via java so I have hope the data you need for the elements here are potentially available the question if of course if they are vended. While their implemented exporter SEEMS like a less efficient solution then this exporter. And I am not sure if there is CURRENT active work/commits, unlike the author HERE who just turned a release back in Jan and was kind enough to document is vended Metrics.... The other exporters do like 95% of what you want and thus I chose to use it instead of this repo's exporter.

IDEALLY love to see a FUNCTIONAL merge of these but VERY unlikely given very different code bases so the only hope would be if the author here would be interested in taking on all the metrics from The fork or Original and implement them in his exporter.

As an Engineer myself I'm happy to offer any assistance that's helpful, but not a python person so unfortunately I can't take the actual dev on myself.

All the best and good luck. I'll be watching (and when I get some free time digging into the actual vended metrics from the other exporter which I'll likely post as a issue with the likely title: Proposed Documentation revision/addition: Metrics

Finally thanks to @esanchezm for your continued work here. While I didn't choose to use it for my deployment, please don't take that as slight on your work here. I truly wish I COULD use if and if I can help please let me know!

--T

@esanchezm
Copy link
Owner

Thank you very much for your comment, @taw123 and also to @daviddanko. These kind of traction is really pumping and I really appreciate the effort on writing such messages and showing your interest.

Honestly, I don't find any utility on having these kind of metrics because they could create an explosion in labels cardinality (specially for leechers 😬 ). However, I think it's also very important to listen to those interested in the project, so event though I can't promise to deliver, I'll try to work on it now that I have some extra spare time.

Per-torrent metrics are however a bit tricky because there could be MANY things to consider (number of files, percentage of each file, global percentage, start and end date, ratio...) 😮‍💨 I think I'l start easy haha

As for contacting the exporter made in Java and try to make metrics compatible in terms of dashboards... Well, honestly I'm not much interested because I don't think there's much need for it. One thing you could do, though, is open another ticket here with the suggestions you have for the dashboard and we could talk about it there because it may lead to the need of further metrics. Sounds good?

Again, I can't promise anything and any help is appreciated!

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

3 participants