[ZBX-24717] Setting of items that use Change per second differs from manual. Created: 2024 Jun 25 Updated: 2024 Nov 25 Resolved: 2024 Nov 25 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 6.0.30 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Major |
Reporter: | Osamu Uehara | Assignee: | Aleksejs Abrosimovs |
Resolution: | Declined | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
Description |
This ZBX ticket is a request to fix the some default template. Note: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers. However, several templates have different settings.
Wouldn't it be necessary to change to Numeric (float)? |
Comments |
Comment by Aleksejs Abrosimovs [ 2024 Nov 25 ] |
As mentioned, the manual states: Note: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers. But, it also states:
This is especially relevant for small numbers where the decimal part matters.
and: If the floating-point values are large and may exceed the 'float' field length in which case the entire value may be lost, it is actually suggested to use Numeric (unsigned) and thus trim only the decimal part. Taking into account that the metrics of the matter are bits and packets - smallest unsplittable entities and that the amount of them is usually huge, we can assume that the possible decimal part of the calculated result is not significant for troubleshooting and analysis and can be safely ignored in most cases. And for these rare cases, any template can be altered by user to meet one's needs. |