Releases: lordmilko/PrtgAPI
Releases · lordmilko/PrtgAPI
PrtgAPI 0.9.20
Improvements
- Respect
PrtgClient.RetryCountandPrtgClient.RetryDelaywhen resolving objects
Bugfixes
- Fix
SensororDeviceOrGroupOrProbe.inheritIntervalcrashing when an inherited interval specifies that scanning should occur at a fixed interal (#375) - Fix
LogStatus15not working
PrtgAPI 0.9.19
PrtgAPI 0.9.18
Improvements
- Implement top secret
nosession=1parameter on/editsettingsAPI calls to reduce PRTG Core Server memory usage when modifying settings in bulk
Bugfixes
- Fix PrtgAPI PowerShell Progress crashing when piping from Variable -> Unsupported (e.g.
Out-GridView) -> Action (#274) - Fix
Connect-GoPrtgServercrashing when encrypted passhash cannot be converted into aSecureString(e.g. it was copied from another user/computer's profile) - Fix PRTG failing to resolve created objects when name starts or ends with whitespace due to PRTG trimming name (#276)
- Fix
ObjectProperty.Locationnot setting location value properly when the current culture's number format does not match invariant culture (#275) - Fix
AddSensorfailing when the 302 redirect fromaddsensor5.htmtodevice.htmfails witth HTTP status 556 as a result of the PRTG server being under high load. (#280) - Fix
ConvertUtilities.ToDynamicDoublecrashing inTryRoundDecimalwhen trying to equate 1,000 and 999.8 due to 000 simplifying to 0 - less than 2 digits (#283) - Don't throw a 403 forbidden when querying whether a PRTG Server is using English when using a non-admin user in PRTG 22.3.79 (#308)
- Fix
SensorQueryTargetvalues specified toGetDynamicSensorParameters()not being used when eventually callingAddSensor()(#312)- Implement support for specifying the
SensorQueryTargetor otherISensorQueryTargetParametersto use onRawSensorParameters, which is now mandatory for sensor types expecting sensor query targets in PRTG 22.3.78.1873
- Implement support for specifying the
PrtgAPI 0.9.17
Improvements
- Implement support for modifying and retrieving
ObjectProperty.PrimaryChannelSet-ObjectPropertywill resolve the-PrimaryChannelfor you based on a wildcard expression that can be specified
Bugfixes
- Fix
ConvertUtilities.ToDynamicDoubleinGet-SensorHistorycrashing when a display value containing a decimal point with more than 3 decimal places is passed in but with a raw value whose value is an integer (#223) - Fix Threshold not being set to
double?inNotificationTriggerDataused when deserializing triggers running on non-English versions of PRTG (#230) - Fix PrtgAPI PowerShell progress not being completed properly when an exception is thrown during an
EndProcessingblock (such as when-Batch:$true) or whenErrorActionPreference = "Stop"in any stage - Fix sensor factory channel definitions set by PrtgAPI corrupting the PRTG Configuration file in older versions of PRTG due to
\r\nseparating newlines being expected rather than simply\n - Fix colon dates on
SystemInfoobjects sometimes being an error string rather than null or empty (#237) - Fix
Get-SensorHistorynot taking into consideration channel scaling multiplication and division values when figuring numeric display value from unknown culture viaConvertUtilities.ToDynamicDouble(#241) - Fix
Get-SensorHistoryfailing to retry creating format XML after an exception previously occurred during the first generation attempt - Fix pipe from variable progress crashing due to
ArrayEnumeratorchanges in PowerShell Core 7.2.0 (#252) - Fix
Channel.Unitnot setting properly when channel does not contain acustomunitfield at all - Fix
GetObjectPropertyXML sanitization not working properly on multiline strings (#262) - Fix API requests that rely on cookie authentication failing in 22.1.74+ (#268)
PrtgAPI 0.9.16
New Features
- Implement support for generating sensor history reports showing precise uptime/downtime within a specified time range. Accessible via the new
PrtgClient.GetSensorHistoryReportmethod or via the new-Reportparameter on theGet-SensorHistorycmdlet. For more information, please see the wiki
Improvements
AddSensor/Add-Sensornow hints that you may need to specifyDynamicTypeon your request parameters when it is unable to resolve the created object (a common occurrence withsnmplibrarysensors)- PrtgAPI now stores more precise build numbers (especially useful for differentiating between various pre-release builds) via
AssemblyInformationVersionattributes, exposed when troubleshooting viaGet-PrtgClient -Diagnostic
Bugfixes
- Fix
ConvertUtilities.ToDynamicDoublenot using "normal" rounding (MidpointRounding.AwayFromZero) resulting in a failure to properly parse values in some scenarios (#218) ConvertUtilities.ToDynamicDoublecan now convert theoretically any single character thousands/decimal group separator combination (#221)- Fix
GetProbenot returning all probes in some environments due to new probe retrieving logic implemented in PrtgAPI 0.9.15 (#219)
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
InheritIntervalisfalse(#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-Probenot working in PRTG 21.2.67 (#215) - Add "equal to" and "not equal to" as possible deserialization values for
TriggerCondition.EqualsandNotEqualsrespectively in newer versions of PRTG - Fix deserialization engine throwing a
NullReferenceExceptionwhen failing to deserialize an unknown value of an enumObjectProperty - Fix
SetChannelProperty/Set-ChannelPropertyignoring 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-SensorHistoryfailing 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)
PrtgAPI 0.9.14
Improvements
General
- Implemented
ClusterNodeproperty onLogobjects
C#
- Implemented
FlagEnum.Createstatic methods for creatingFlagEnum<T>objects
PowerShell
- Implemented support for specifying null or empty passwords to
New-Credential - Implemented -Hashtable parameter on
New-SensorFactoryDefinition. Allows generating complex sensor factory definitions in a single go that would normally require multipleNew-SensorFactoryDefinitioninvocationsC:\> Get-Sensor -Tags wmimem* | fdef @{name={$_.Device}},@{name="Line at 40.2 [msec]";value=40.2}
- Implemented PowerShell type conversion on cmdlet parameters that internally get passed to other cmdlets (such as
New-Sensor -Factory ..., which involves internally invokingNew-SensorFactoryDefinition)
Bugfixes
General
- Fix API requests involving cookies not working when a user incorrectly specifies to use
http://instead ofhttps://against a HTTPS PRTG server (Fix #181) - Fixed notification action property categories (
Email,SMS, etc) not triggering lazy loads onNotificationActionobjects retrieved notification triggers - Fix
ServerStatus.DateTimecrashing when the serverDateTimeformat differs from the client format (e.g. US vs UK time format)
PowerShell
- Fix
Get-Sensornot retrieving sensors from groups via intermediate devices when specifying-Recurse:$false(Fix #159)
PrtgAPI 0.9.13
Improvements
General
- Add support for extracting an enhanced error message when adding sensors/resolving sensor targets/parameters when an error message is not included in the
AddSensorProgressresponse (#140)
C#
- Add
startDateparameter toPrtgClient.WatchLogs(#139)
PowerShell
- Add
-rtalias for-RawTypeparameter onGet-SensorTarget/New-SensorParameters - Fix PowerShell Progress failing when piping from a variable containing an
Array/SZArrayEnumeratorin .NET Core 3.1 (#136)
Bugfixes
- Fix
GetNotificationTriggerscrashing when PRTG fails to properly HTML encode quotes in sensor names (#131) - Fix
NotificationTriggerTranslatornot storing unique name for Notification Action items, resulting in crash when multiple actions exist with the same name (#145)
Breaking Changes
- Change
NotificationAction.SMP.TrapCodefrom anintto anint?due to PRTG not forcing it have a value (#130)
PrtgAPI 0.9.12
New Cmdlets
Compare-PrtgTree: provides a PowerShell friendly way of comparing and reducingPrtgNodeobjects, as well as specifying the types of comparisons to include/exclude
Improvements
General
FlagEnumtypes now properly flatten the list of values specified to their constructor, rather than assuming none of the specified values contain flagsFlagEnumtypes now properly merge negative flags with negative flags passed to them. If only negative flags are specified, all flags but those specified will be included- Added complement operator
~toFlagEnum - Add support for comparing/printing the values of
PropertyValuePairobjects contained inPropertyNodeobjects PrtgNodecomparisons now take into consideration whether their positions under their parents have changedPrtgNodechildren are now automatically sorted according to their positionPrtgNode.CompareTo()now allows specifying the comparisons to include/exclude- Added a
Nodemember toPrettyLineobjects. Stores theTreeNodethe line is represents
PowerShell
- Add
-Reduceparameter toShow-PrtgTree. Pretty prints a reducedCompareNodetree (equivalent$tree.Reduce() | Show-PrtgTree) - Fixed incorrect grammar in
Get-SensorHistoryPowerShell progress - Added custom table format for
PropertyNodeobjects for displaying the underlying value
Bugfixes
General
- Include TLS 1.2 in allowed security protocols on older versions of .NET Framework for compatibility with PRTG 20.1.55 (#128)
- Fixed an issue wherein
GetSensorHistoryincorrectly assigned the same raw value to multiple channels when multiple objects exist with the same channel ID (such as the volume and speed channels of Traffic Sensors) - Fix
CompareNodereduction not detecting differences that are only visible on grandchildren, resulting in trees potentially failing to be reduced at all - Fix data KB/MB/GB/TB data units failing to deserialize on Notification Triggers in PRTG 20.1.55
PowerShell
- Fixed
Get-SensorHistorynot parsing byte display values properly (#124) - Fixed
Get-SensorHistoryconverting values over 1000 to decimals when the last 3 digits of the display value match the decimal places of the raw value, rounded up (#125) - Fixed missing setter on
Get-PrtgTree-Optionsparameter - Fix progress not being displayed with tree cmdlets like
Get-PrtgTreewhen values outside ofTreeParseOption.Commonare specified
PrtgAPI 0.9.11
Bugfixes
PowerShell
- Fixed
Get-SensorHistorycrashing when parsing display values greater than or equal to one million (#123) - Redesigned
Get-SensorHistorydisplay value parsing algorithm to be much more robust against determining whether a display value uses an EU or US number format