Forwarded to devs overusage Notification - sent on wrong value (specific conditions)

[TomBoB]

Username:

TITLE

overusage Notification - sent on wrong value (specific conditions)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.57 #5, AlmaLinux 8.9

PROBLEM DESCRIPTION

The notification "Resource usage limits exceeded by subscription" is being send out to clients on the wrong disk space usage value under certain conditions / setups.

STEPS TO REPRODUCE

- Notification "Resource usage limits exceeded by subscription" turned on
- In a Service Plan, enable disk space usage [example 5GB]
- In same Service Plan, enable notification on certain usage [example 4500MB]
- Create an add-on Service Plan. [example +10GB disk space]
- Apply both the above Service Plan and the add-on to a subscription.
Fill up space on the subscription and wait for notification

ACTUAL RESULT

Notification is sent out to client on : [as per example] 4500MB disk size usage fixed.
===========================
> Subject: <server7.ourcompany.com> Notification: Resource usage by subscription has exceeded the allotments
> Reply-To: postmaster@server7.ourcompany.com
>
>
> The 'clientdomain.com' subscription, owned by user 'Some Client', is approaching or already exceeded the resource usage limits:
>
> Disk space: 15 GB Limit / 4502.7 MB (29%) Used / 10857.3 MB (71%) Remaining
===========================
Although the disk space calculation in the notification is correct, the notification is sent out at the fixed/static value set in the Service Plan, not accounting for the additional disk size allocated as per add-on.

EXPECTED RESULT

Notification is sent out to client on : (5GB service plan + 10GB Addon) - [difference of 5GB service plan - 4500MB notification]
So the client gets a warning on a properly calculated disk size value available for their usage. [14500MB in the example]

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[TomBoB]

On reflection, if the notification value would be %-of-disc-size-based instead of a fixed value, that would make above a lot easier to do/handle.
But a switch like that may of course have other impacts elsewhere I'm not aware of.

 

[Peter Debik]

- Did you synchronize the service plan(s) with your subscription?
- Did you set a higher notification threshold on the add-on or was that field left empty?

 

[Kaspar]

That is strange behaviour indeed. A add-on Service Plan should actually have an option to change the notification limit as well.

 

[TomBoB]

- Did you synchronize the service plan(s) with your subscription?
Yes subscription is synced to the service plan

- Did you set a higher notification threshold on the add-on or was that field left empty?
There is no option / no field for setting a notification threshold when using an add-on

 

[Peter Debik]

- Did you set a higher notification threshold on the add-on or was that field left empty?
There is no option / no field for setting a notification threshold when using an add-on

You are right. I never realized this is missing. I'll ask the team whether this is intentionally.

 

[Kaspar]

@Peter Debik did you receive any feedback from the team on this?

 

[Peter Debik]

Hmm, not yet, I'll have asked how to proceed. Thank you for reminding me.

 

[Peter Debik]

It's a flaw in the business logic. Now forwarded as an issue for further handling, internal ID PPS-15511.

 

[Peter Debik]

The behavior has been confirmed as a product issue and will be fixed in a future Plesk update. Internal ID PPM-14301.

 

[TomBoB]

Hi, it's a year later. Client just forwarded me the notification again and asks when it will be resolved.

 

[Sebahat.hadzhi]

Thank you for the update, @TomBoB . Due to its low impact the issue has not been prioritized over the past year. Hence, the fix was delayed. At this particular point, the priority of the case still remains relatively low and it is not in our team's short-term list of bug fixes. Unfortunately, I still cannot provide any ETA. I know this is not ideal, but might I suggest adjusting the "Resource usage limits exceeded by subscription" notification and adding a disclaimer about the disk space addon. At least, that might save some user confusion until an official fix is released.