Skip to content

PrtgAPI 0.8.6
Compare
Choose a tag to compare
@lordmilko lordmilko released this 04 May 12:03
v0.8.6
13a1cd7

New Features

PowerShell

  • Implemented support for specifying a hashtable of -RawParameters to Set-ObjectProperty

New Methods

  • PrtgClient.GetSchedules: Retrieve all monitoring schedules supported by PRTG

New Cmdlets

  • Get-PrtgSchedule: Retrieve all monitoring schedules supported by PRTG

Improvements

General

  • Implemented support for retrieving Proxy Settings for HTTP Sensors, Scanning Intervals and Schedules, Dependencies and Maintenance Window settings from devices, groups and probes

PowerShell

  • New-SearchFilter now accepts a -Value of type object rather than string
  • Implemented support for opening notification actions and schedules via Open-PrtgObject
  • Removed unnecessary call to PrtgClient.GetGroups in Get-Sensor when specifying -Resolve:$false

Bugfixes

General

  • Fixed an issue wherein NotificationAction objects returned as part of a NotificationTrigger did not lazily deserialize all of their properties
  • Probe parameters now prevent filtering by a ParentId other than 0
  • PrtgAPI now correctly serializes DateTime and TimeSpan objects specified in search filters
  • A more descriptive error message is now thrown when attempting to filter by a Status of 0

PowerShell

  • Fixed several instances of cmdlets not properly unwrapping PSObject values
  • Fixed a bug wherein Channel parameter of Set-ChannelProperty was not mandatory on Default and Dynamic parameter sets
  • PrtgAPI now consistently displays all results when performing queries like Get-Sensor ping -Count 1. For more information, see Case Sensitive Filtering below

Case Sensitive Filtering

When filtering on a table cmdlet using FilterOperator.Equals PRTG can become case sensitive when multiple filters are used together (such as Name + Tags). Since the common parlance of PowerShell is to be case insensitive, PrtgAPI circumvents this by filtering using FilterOperator.Contains even if a wildcard is not specified.

If a -Count is used in conjunction with a literal -Name (e.g. Get-Sensor ping -Count 1) query's results may contain items whose names do not actually match (e.g. SSH Ping). As PrtgAPI will automatically remove any non-matching items, fewer results than expected may be displayed.

In order to accommodate the common case of Get-Sensor <name> -Count <count>, when PrtgAPI detects that -Name and no other filter besides ParentId has been specified, the Name filter operator will be changed to FilterOperator.Equals.

Assets 3
Loading