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

Set custom quota warning values #9

Closed
sunjam opened this issue Jun 3, 2017 · 12 comments
Closed

Set custom quota warning values #9

sunjam opened this issue Jun 3, 2017 · 12 comments
Assignees
Milestone

Comments

@sunjam
Copy link

sunjam commented Jun 3, 2017

Is this already an option? I'd like to set my own quota values rather than use the default.

@nickvergessen
Copy link
Member

Which value would you choose?

@sunjam
Copy link
Author

sunjam commented Jun 3, 2017 via email

@AceSlash
Copy link

I think that a 50% warning is not that useful, at least for me.

@nickvergessen
Copy link
Member

@nickvergessen
Copy link
Member

Maybe we change the values to 80, 90 and 95?

@simon-zumbrunnen
Copy link

I think it would be very useful if it was possible to configure an arbitrary number of warnings at custom values. Maybe it could even be changed by the user instead of the admin? Or even better: An option for the admin to allow the users to change it from the default, which the admin decides.

My opinion on a default value would be 80 and 95. But I think we will find endless opinions on that.

@nickvergessen
Copy link
Member

Yeah, I see that problem, that's why I'm open for 2 things:

  1. Adjust existing numbers to something useful
  2. Allow admins to specify 3 numbers.

@AceSlash
Copy link

AceSlash commented Jul 7, 2017

Best of the best would be to specify the number of alerts and the % for each. In my case, I know that my users will simply ignore a warning if it says something else than 95%, so a single alert is sufficient for me.

But of course it depends on so many things that you simply can't have a single policy for everyone.

@Schmuuu
Copy link

Schmuuu commented Aug 4, 2017

I agree with @AceSlash and also think it would be awesome (best solution?) if the users can define the values for themselves, or the admin can set the values per user/ group.

The idea to "Adjust existing numbers to something useful" isn't a good approach in my opinion.
Users with 1GB storage and 75% used space don't have much space left and a warning may be applicable. For users with 500 GB storage even a 90% quota warning is rather nice to know than an actual alert to them.

For admins that have great diversity in the defined quotas, it is difficult to chose the right percentage to notify.

@Gardakant
Copy link

While changing values in checkQuota.php is a solution it's a bad one: this generates a Security & Configuration problem :)

root@host1:/var/www/nextcloud# sudo -u www-data php occ integrity:check-app quota_warning

  • INVALID_HASH:
    • lib/CheckQuota.php:
      • expected: d54a8e91ded58799ca71aeda7c51b0e9fb286aea126f15321b1798f2f204b2376bfb3c0710b9b6a09c40fecc0c0998ce8867cbdec6920b7932ee9800face1bdf
      • current: da7479000fbce371208e718b4bdec9216373d92444dc71e8c8ba6295310cd4dc2885585bf9de0aaa7df36b3955d60462910d29bcb4c2bbdf52ba3c87eac8f470
        root@host1:/var/www/nextcloud#

@nickvergessen nickvergessen self-assigned this Aug 16, 2017
@nickvergessen nickvergessen mentioned this issue Aug 17, 2017
@JK74
Copy link

JK74 commented Aug 21, 2017

I do agree with Schmuuu his posting! Maybe allow some settings on this like below 90% by the user? and a setting like 90 or 95% by the admin? What about notifications? Do we get them on e-mail as well (not existing today)? thnx

@MorrisJobke MorrisJobke added this to the Nextcloud 13 milestone Aug 29, 2017
@DJCrashdummy
Copy link

to address @Schmuuu's problem with great diversity in the defined quotas (#9 (comment)), maybe it will make sense to add a value (in MB/GB/etc.) which must be undershot first to trigger a warning-action; maybe one value overall or different ones for every percentage...

but the whole thing would make it more and more complicated. - ...i'm just thinking aloud.

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

No branches or pull requests

9 participants