New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


CPU Percentage change based on Limit applied

Votes:

0

Your Vote:

Up

Down

This might be a bug and if not could someone explain to me how it works?

I have numerous windows CPU load sensors, Primary Channel is Total Percentage.

When i edit the channel and select "Enable alerting based on Limits" and then put a number inside the limits percentage and apply, The scale of the dial for the channel doesn't look right.

Example

Before. .

After changing upper error limit. .

Not sure why this would change, or how 104% is even possible.

bug cpu-sensor limits

Created on Apr 25, 2019 12:32:52 PM by  matt631 (50) 1 1

Last change on Apr 25, 2019 1:41:46 PM by  Dariusz Gorka [Paessler Support]



7 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi there,

When you add an error limit to a channel, then PRTG always add some percent to gauge in order to display this area. Example:
You have a channel with a maximum value of 50. The gauge will go from 0-50. You add a limit of 50 to the channel, now you wouldn't see any error area in the gauge. This is why PRTG adds a certain amount to make it visible.

Best regards.

Created on Apr 25, 2019 1:52:44 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, Thanks for the quick reply.

I understand your example and it makes sense for measurements without hard boundaries however 100% is a percentage and given that CPU resource is a finite resource There can be no such thing as 120% CPU usage.

If a user sets an error state at 99% then I wouldn't expect to see anything but a small slither on the dial or a disproportionate scaling on the dial. If a user sets a error at 99% then when the measurement breaches that marker i would expect an alert but at the same when the measurement reached 100% then that's its limit.. 120% in this example means 100% so it misleading to anyone reading the data.

I understand that you are using the same dial and logic for percentage and infinite measurements but this does appear to be poor development if customers can end up with a figure above whats actually possible.

Created on Apr 25, 2019 2:25:41 PM by  matt631 (50) 1 1



Votes:

0

Your Vote:

Up

Down

Hi there,

I surely understand your point, but for the gauge it is not really important what kind of sensor it is or what channel. There are currently no plans to change this behavior within PRTG.

Best regards.

Created on Apr 25, 2019 3:02:27 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks, can you help me understand then why issues like the below image occurs. The settings are set to warn at 80 and error at 90...

.

Why does my machine goto 122% exactly?

If the difference between warning(80) and error (90) is 10% aka represented by the yellow then why is the red so big and why does it appear to have grown even more so since my original image.

Thanks

Created on Apr 25, 2019 3:35:59 PM by  matt631 (50) 1 1



Votes:

0

Your Vote:

Up

Down

Hi there,

Could you check the "Maximum"-column of that channel? I suspect that it went above 100% one time. If this is the case, then please note that these values come directly from the device itself.

Best regards.

Created on Apr 26, 2019 6:05:09 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi you are correct, The column did go above 100% so just to be clear are percentage values also just read from the device? Ie there is no computational work done by PRTG to get the percentage value?

Kind Regards

Created on Apr 26, 2019 8:15:14 AM by  matt631 (50) 1 1



Votes:

0

Your Vote:

Up

Down

Hi there,

The value is 1 to 1 taken from the device. This is a common issue, especially under Windows when the target device is totally overloaded.

Best regards.

Created on Apr 26, 2019 9:03:24 AM by  Dariusz Gorka [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.