PrtgAPI 0.9.15
Improvements
General
- PrtgAPI now includes hidden channels in API results (#194)
- Implemented support for modifying
ChannelProperty.ShowInTable
- Implemented support for modifying
ChannelProperty.Name
(#201) - Sensors, Devices, Groups and Probes now show their inherited scanning intervals when
InheritInterval
isfalse
(#197) - PrtgAPI now trims trailing slashes in the PRTG server name (
prtg.example.com/
->prtg.example.com
) (#206)
Bugfixes
General
- Add
LogStatus.FtpConnectionMode
(#214) - Fix
GetProbe
/Get-Probe
not working in PRTG 21.2.67 (#215) - Add "equal to" and "not equal to" as possible deserialization values for
TriggerCondition.Equals
andNotEquals
respectively in newer versions of PRTG - Fix deserialization engine throwing a
NullReferenceException
when failing to deserialize an unknown value of an enumObjectProperty
- Fix
SetChannelProperty
/Set-ChannelProperty
ignoring all errors returned from API requests; now only ignores errors returned when properties that are known to cause erroneous PRTG errors are specified (likeChannelProperty.PercentValue
)
PowerShell
- Fix
Get-SensorHistory
failing to calculate display values in some circumstances due to a rare rounding error (#218)
Known Issues
Due to a bug in (at the very least) some of the latest versions of PRTG, due to the new way in which PrtgAPI retrieves probes (which is required due to changes in PRTG 21.2.67+) PrtgAPI may not always return all probes from your PRTG server. This issue has been reported to Paessler; for now, if you find PrtgAPI 0.9.15 does not return all of your probes it is recommended you use PrtgAPI 0.9.14 with a version of PRTG prior to 21.2.67 (that does not have the new PRTG Core Server device)