-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get-SensorHistory produces an unexpected error: Input string was not in a correct format. #123
Comments
Hi @robm82, Can you please run the following commands and provide the output Set-PrtgClient -LogLevel Response
Get-SensorHistory -Id 11079 -Verbose
$error[0].Exception.StackTrace Regards, |
Thanks for the quick response @lordmilko :). Below is the output of those commands:
|
In an attempt to make While I figure out a solution to this, are you able to advise whether the command |
Yes that command does work - thanks for verifying and providing a workaround. |
…r than 1,000,000 (#123) -Redesigned Get-SensorHistory display value converter to be more robust at deciphering whether a value is a US or EU number format -Added additional tests for current ConvertUtilities.ToDouble implementation
Hi @robm82, I have now pushed a release candidate for PrtgAPI 0.9.11, which contains a fix for this issue Are you able to potentially download the latest build and follow the manual installation steps to confirm whether the command In addition, it would be helpful if you could potentially get Get-Sensor | Get-SensorHistory Obviously this may potentially generate some load on your system, although I managed fine on my system with over 8000 sensors. While some sensors may complain they didn't have enough monitoring data, the whole thing will stop if it runs into a channel value it does not know how to parse Please let me know how you go Regards, |
Hi @lordmilko - I have just tested Thanks again for looking into the issue so quickly. |
Thanks @robm82! Please be advised PrtgAPI 0.9.11 has now been released. To update your system wide installation simply run Regards, |
I am trying to write a script to get disk space usage over the past 30 days, which does work but on a handful of sensors I get a weird error. I have also tried to use
Get-SensorHistory -id 11079
which again produces the same error, so I know that it isn't my script, but there appears to be something wrong with the PrtgAPI PowerShell module? Below is the full output:Here is the output of Get-PrtgClient -Diagnostic:
The text was updated successfully, but these errors were encountered: