Jackett: [Feature Request] Monitoring Support

Created on 8 Sep 2018  路  3Comments  路  Source: Jackett/Jackett

Hi!

If this is already possible, please point me to a documentation.

I'm currently implementing Pandora FMS for my network -- a monitoring solution. I can already nicely monitor qBitTorrent, I get the current up/download speeds, the amount of errored / stalled torrents, etc. What I'd also like to add, is some sort of Jackett monitoring, as this is a central part of my system.

For example (if you can think of other useful metrics, please tell):
1) Requests to Jackett the last minute / 15 minutes / hour
2) Results returned from Jackett the last minute / 15 minutes / hour
3) Which Systems called Jackett (is this even recorded) and how often, e.g. Medusa, Lidarr, ...
4) List of currently configured Search Engines, if they are currently working, maybe even lag?
5) Possibility to start the "test torrent search engines" via API call (with a TimeOut of e.g. 5 seconds) and get back a list of successful and unsuccessful tests
6) Outgoing / Incoming Bytes in total since startup
7) "Uptime" of Jackett

I think, the qBitTorrent works quite nice for things like that, here's the link to their documentation: https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation

Thanks!

Enhancement Help wanted

All 3 comments

None of the data except of the indexer list is currently recorded.
http://127.0.0.1:9117/jackett/api/v2.0/indexers (needs a valid cookie for authentication) will provide a list of indexers/error message.
An alterantive would be to use the special t=indexers API
http://127.0.0.1:9117/jackett/api/v2.0/indexers/all/results/torznab/api?apikey=XXX&t=indexers
But it only contains the configured/unconfigured flag, no error state (but it can be easily added).

Marking this as enhancement request, a PR would be welcome.

Thanks for the answer. What is a PR?

@annomatik PR = Pull Request

Was this page helpful?
0 / 5 - 0 ratings