This is a maintenance release, with new features introduced, and bugs fixed.

Monitors

• Custom SNMP Trap monitors: SNMP v3 traps are now supported

Templates

• Templates have been added for MS Exchange 2013 application; added to “Other Applications and Services” category

Client Application and Monitoring Service

• HTTP(S) monitor now does not report SSL errors for valid site certificates, when “Ignore HTTPS (SSL) errors” option is turned off
• Improved stability of monitoring service, in case when monitors hang for a very long time
• Support for the following variables has been added:

   

  $WindowsDomain : string
  $WindowsUser : string
  $WindowsPassword : string (password as plain text)

   

  $UnixUser : string
  $UnixPassword : string (password as plain text)
  $UnixAuthType : string, one of ‘password’, ‘key’ or ‘key_or_password’
  $UnixKeyPath : string (path to private key file)
  $UnixKeyPassphrase : string

   

  $SNMPVersion : string, one of ‘v1’, ‘v2c’ or ‘v3’
  $SNMPCommunity : string
  $SNMPv3Authentication : string, one of ‘none’, ‘md5’ or ‘sha1’
  $SNMPv3User : string
  $SNMPv3Password : string (password as plain text)
  $SNMPv3PrivacyProtocol : string, one of ‘none’, ‘des’ or ‘aes’
  $SNMPv3EncryptionKey : string

   

  These variables are available in monitors and actions that use corresponding types of credentials. For example, you can pass `$WindowsDomain`, `$WindowsUser` and `$WindowsPassword` as command-line parameters to the script in Script or Program monitor. This way you reuse credentials defined for IPHost when invoking external scripts/programs and there is just one place to define them.

  When a variable is undefined or irrelevant for monitor type used, it is not expanded by IPHost.