Exact Value in Threshold become different after upgraded from 0.8.8h to 1.2.27

Post general support questions here that do not specifically fall into the Linux or Windows categories.

Moderators: Developers, Moderators

Post Reply
jason23
Posts: 44
Joined: Wed May 22, 2024 9:52 am

Exact Value in Threshold become different after upgraded from 0.8.8h to 1.2.27

Post by jason23 »

Hello Sir,

I have upgraded from v0.8.8h to v1.2.27, but I discover that the Exact Value in Threshold setting become different.

In Version 0.8.8h, exact value = Bytes (B)
For example, 337500000 Bytes (B) = 2700 Megabits (Mb)
Ref Link: https://www.kylesconverter.com/data-sto ... s-to-bytes

In Version 1.2.27, when I type the same value 337500000, it will turn to 337.5M automatically after being saved.

May I know if this is a bug or anything I need to do ?? to fix with the issue.

Thank you.
User avatar
TheWitness
Developer
Posts: 17047
Joined: Tue May 14, 2002 5:08 pm
Location: MI, USA
Contact:

Re: Exact Value in Threshold become different after upgraded from 0.8.8h to 1.2.27

Post by TheWitness »

This is normal. In the backend it stores the data raw though. If it's off from the backend perspective, check the base units in your graph template.

So, bottom line it's not an issue.
True understanding begins only when we realize how little we truly understand...

Life is an adventure, let yours begin with Cacti!

Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages


For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests