Skip to content
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.

Per-server quotas #352

Closed
rcdailey opened this issue Mar 20, 2017 · 8 comments
Closed

Per-server quotas #352

rcdailey opened this issue Mar 20, 2017 · 8 comments

Comments

@rcdailey
Copy link

I use nzbget with a primary (monthly) paid unlimited server + several block accounts. The block accounts serve as only backups for missing articles. I set them lower down in priority. I have so many of these, that it gets difficult to browse to each website to check on my quota.

Note that all of my block accounts have a quota with no time limit. For example, you can purchase 500GB and use that up over the course of 1 month or 1 year, it doesn't matter.

What would be ideal is to specify a "starting quota" to each server (optional), representing the remaining bytes available on that block account. As actual articles are downloaded on said server, it would subtract the amount of bytes from the quota. Slowly it will approach 0 bytes remaining, and maybe nzbget could allow a per-server threshhold, which will trigger that server to be effectively disabled until I can get around to purchasing more quota for it.

Think of this as tracking the mileage on your car until your next oil change.

Would this be a reasonable feature to add? I have seen similar implementations for quota, specifically #99, but this is a global quota, not per-server.

@hugbug
Copy link
Member

hugbug commented Mar 20, 2017

What happens currently when the block is exhausted? Do servers return specific error messages allowing to distinguish the issue from other errors? Please provide message examples if you have any.

If it's possible to distinguish such errors it would be possibly better to react on them instead of trying to disable servers upfront. The usage data calculation in NZBGet and on provider servers may differ slightly. We don't want to disable servers which still may have remaining amount. In other case it may happen that the servers reach the 0 mark before NZBGet does; then we need again NZBGet to understand error messages.

@rcdailey
Copy link
Author

rcdailey commented Mar 22, 2017 via email

hugbug added a commit that referenced this issue Apr 7, 2017
New button “Volume Statistics” in section “News Servers” of settings
page. Shows the same volume data as in global statistics dialog.
hugbug added a commit that referenced this issue Apr 7, 2017
for user comments on news servers.
hugbug added a commit that referenced this issue Apr 12, 2017
 as a performance optimization measure to reduce amount of transferred
data.
@hugbug
Copy link
Member

hugbug commented Apr 12, 2017

I can offer a solution as an extension script ServerAlert.py - server volume alert.

Also made a few small improvements to NZBGet, which make the script easier to use and optimise performance.

@hugbug
Copy link
Member

hugbug commented Apr 24, 2017

@rcdailey, have you tried the script?

@rcdailey
Copy link
Author

rcdailey commented Apr 24, 2017 via email

@rcdailey
Copy link
Author

rcdailey commented May 12, 2017

Hey @hugbug, sorry it's taken me so long to get back with you :-(

I have installed the script but I do not see the "Volume Statistics" option under any of my servers. The extension settings page does appear in the options tab, though, so I know that NZBget can detect that the script is installed.

I am using NZBget 18.1

@hugbug
Copy link
Member

hugbug commented May 12, 2017

You missed that line in script description:

The script requires at least nzbget v19.0-r1940.

@rcdailey
Copy link
Author

rcdailey commented May 12, 2017 via email

@hugbug hugbug closed this as completed May 31, 2017
hugbug added a commit that referenced this issue Oct 9, 2017
New button “Volume Statistics” in section “News Servers” of settings
page. Shows the same volume data as in global statistics dialog.
hugbug added a commit that referenced this issue Oct 9, 2017
for user comments on news servers.
hugbug added a commit that referenced this issue Oct 9, 2017
 as a performance optimization measure to reduce amount of transferred
data.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants