Hello

TimeSeconds channel unit is not properly processed when the Unit is Float. Is this intentional?

Sensor

Sensor code:

Write-Host @"
<prtg>
	<result>
		<channel>Good</channel>
		<value>8192</value>
		<Unit>TimeSeconds</Unit>
	</result>
	<result>
		<channel>Bad</channel>
		<value>8192</value>
		<Unit>TimeSeconds</Unit>
		<Float>1</Float>
	</result>
	<result>
		<channel>Bad Also</channel>
		<value>8192.35</value>
		<Unit>TimeSeconds</Unit>
		<Float>1</Float>
	</result>
	<result>
		<channel>Good2</channel>
		<value>956849</value>
		<Unit>TimeSeconds</Unit>
	</result>
</prtg>
"@

PRTG:

PRTG Version	PRTG Network Monitor 22.1.75.1594 x64
Auto-Update Status	Version 22.1.75.1594 successfully installed
Operating System	Microsoft Windows Server 2019 Standard Evaluation (10.0 Build 17763), 2 CPUs (Double x64 Model 45 Step 6), code page "Windows-1252", on VMware
Server Time	04.04.2022 15:14:02 (Central Europe Standard Time)
Server CPU Load	3%
User Name	PRTG System Administrator
Active User Sessions	PRTG System Administrator
Browser	Apple Safari Google Chrome (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.84 Safari/537.36)

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hell Jakub,
thank you for your KB Post.

That is intentional indeed, the time units only work with integers. It's not intuitive but you can use TimeResponse as unit if you need more precision than a second. Think of TimeResponse as milliseconds. You can see a sensor example that uses it here.

Best Regards,
Luciano Lingnau [Paessler]


Apr, 2022 - Permalink