version 2.22.11041.0

New Features

​Monitoring

• Agent Polling
  • Native database monitoring
    • Requires a device Agent to be installed on the database server
    • Supports monitoring of the following databases
      • Microsoft SQL Server
      • MySQL
      • PostgreSQL
    • Database credentials are configured using Agent Access Profiles
  • Windows Updates
    • Reboot reboot requires one-time passwor​d
      • Managed using the Windows Update Profiles page
      • By enabling this setting, the user requesting windows updates on a machine will need to be two-factor authenticated to the platform, and will have to re-enter their one-time password before allowing them to select a reboot as part of windows update
  • Eventlog to Syslog Relay
    • When Syslog relaying is enabled, the platform can forward event logs as Syslog to other systems for processing
    • For example, a service provider might nominate an agent installed on their own network to act as the relay device for many customers, and relay Syslogs to the service provider's own systems for further analysis and processing
• Api Polling
  • Ftp Polling
    • New helper methods implemented to allow monitoring of devices that use legacy monitoring methodologies
  • Additional Custom Polling Configuration
    • An option to create a polling configuration Json object has been added to the Api definitions page
    • This Json object may contain any additional information required to poll specific Apis, and is available to use in the api polling scripts
• AWS Polling
  • Implemented polling of virtual interfaces
• Syslog
  • Implemented handling of multi-line Syslog. Some Syslog implementations include multiple Syslog messages in a single packet, particularly when using TCP. The poller will now split these into separate packets when processing and relaying​
• Syslog Relay
  • Allow relaying to multiple IP addresses
• NetFlow Relay
  • Allow relaying to multiple IP addresses
• Poller
  • Enable Syslog over TLS

Email Integration

• System integration and automation using inbound and outbound email
  • Check mailboxes using IMAP or POP3
    • Customisable actions using scripting
    • Integrates to service desk for ticket creation and updates
  • Enable outbound email messaging from a ticket

Service Desk

• Email Integration
  • Creation of tickets from inbound emails
  • Update of tickets from inbound emails
  • Replies to emails from the ticket
  • Direct emailing from a ticket to ticket's contacts
• Ticket Escalation
  • Defined at Ticket Group level, for each User Group that has access to tickets
  • Customisable per ticket type
  • New event type created to capture the ticket escalation event for event processing and notification
• Ticket Category
  • Defined at Ticket Group level
  • Flexible, hierarchical structure
  • Customisable per ticket type
  • Available for ticket creation in the user input form

Website

• System Integration: Device Live Query
  • Enables an on-demand live query to be performed from the Device page to external systems, such as
    • Vendor specific maintenance contract APIs
    • Enterprise CRM / ERP systems
  • Allows configuration of dynamic menu items to be added to the Device page to perform the query and display the results
  • Uses Integration Profiles to define the match criteria for a device to be applicable for the query, for example based on a device's cost centre, business service, Snmp vendor product, etc.
• System Integration: Email Clients
  • Ability to set up email clients for integration
    • Used for inbound and outbound emails
    • Flexible c# scripting allows processing of emails in the  "OnEmailReceived" script
    • Email clients can be made available to tickets for direct emailing from a ticket by configuring the "IsValidForTicket" script
  • System Integration
    • Allow access to Device Snmp Details from integration scripting
• Connector Quick Links
  • Changed the Url that launches the Connector application to allow bookmarking and creating permanent links to device connections
    • The Url format used is 
      https://<website>/Connect/Device/<deviceId>/<connectionType>[/Port/<port>][/<parameters>]
    • The following connection types support quick linking
      • telnet
      • ssh
      • rdp
      • http
      • https
    • An optional port may be added to the Url if multiple ports are configured for the connection type
    • Optional parameters may be passed for http and https connections. These parameters are appended to the Url when the connector initiates the connection to the device, in case the web site requires an additional path or query string to be supplied
    • An encoded version of the quick link Url may be copied from the website, from each device's Connector pop-up and then used from anywhere as long as the Connector click-once application is installed
      • The link is encoded to help obfuscate the connection information, should the link be used outside of the platform
    • Regardless of whether the link is used within the platform, or externally, an authenticated login session to the platform is required
      • Unauthenticated users will be redirected to the login page to authenticate before the connection is established
• Agent Access Profiles
  • ​New page to configure credentials to be used by agents for database monitoring
  • Profile is assigned to an agent using the agent's Device page
• Syslog Profiles
  • Allows configuring multiple IP addresses for Syslog relay
• NetFlow Profiles
  • Allows configuring multiple IP addresses for NetFlow relay
• Windows Update Profiles
  • New setting made available in the Windows Update Configuration section of the profile to enable the "Reboot request requires one-time password" feature
• Windows Updates
  • Implemented "Reboot request requires one-time password" feature 
  • Export to excel added to grid
• Admin Packs
  • Displays more details
  • Allows comparison of versions
• Multiple pages
  • Change the way passwords are set in various profiles and administration pages​
  • Allowed string columns in grids to be filtered on two values
  • Moved device tools icons ​(ping, trace route, etc) into the device Name column ​
  • Added help tooltip and auto-complete functions to multiple script editors
    • ​This feature can be accessed by pressing [Ctrl Space] while inside an editor
    • Predictive help also pops up if a match is found while typing in the script editor
• ​Devices page
  • Added vendor products column to grid
• Status page
  • Added vendor products column to grid
  • Added business services to grid
  • Added new filtering capabilities
• Password Vaults
  • Requires two-factor authentication for identity provider users
• Device page
  • Implemented integration live query menu items and related query result displays
  • Added section for setting agent access profile
  • Added a side-by-side comparison of different versions of stored config harvest documents
  • Removed some duplicate system information sections
  • Converted journal entries to use html iframe 
• Ticket page
  • Converted description and journal entries to use html iframe 
    • Editing of the description is done using the new Edit button
  • Implemented new email related UI for reading and sending emails from the ticket
    • Email is only available if an Email Client is configured in an applicable Integration Profile
    • New emails may be created and sent only to contacts on the ticket
    • Replies to emails may be sent to the sender and other addressees, as well as contacts on the ticket
• Ticket Groups page
  • Added ticket escalation configuration options
  • Added ticket category configuration options
• ​Notification Profiles page
  • ​Added option to include email tracking identifier for email integration
• ​Identity providers
  • ​User description
  • User import from identity provider
    • ​Integration profiles include user import facility
  • ​Streamline first-time login and group membership assignment​
• ​Contacts: Personal Data
  • Restricted access to the following fields of a contact's information, referred to as "personal data"
    • Title
    • Family name (new field)
    • Given names (new field)
    • Email address
    • Mobile number
    • SMS number
  • A new non-personal data field has been added : Description
  • Use the existing Name and new Description fields to describe the contact if need be without divulging any personal data. Phone number is also considered non-personal data. This is the information that is displayed with the existing "ViewContact" permission
  • To view a contact's personal data, users must be assigned "View Personal Data" permission
  • A user with the appropriate permissions must click on the new "View personal data" button next to a contact's name to view the personal data. This action is audited
  • This change affects all pages where contact information is displayed
  • A new setting has been added to select the way a contact's name is displayed, eg. family name first, followed by given names, or other similar commonly used combinations
• General UI style updates throughout the website

Web API

• Allow disabling Swagger and Swagger UI by setting registry entries
• Web Api exception handling fixes
• Changed DeviceUpdateItem so that properties are optional (nullable). If not supplied, then that property is not updated

General​

• PostgreSQL support for customer (statistics) databases
  • Prior to this version, the platform required MS SQL databases for all its databases
  • Customer databases may now be created as PostgreSQL databases using the Customer Databases page
  • Please note that the primary Gemmb database still requires MS SQL
• Migration of code to .Net 6
  • Web Api, Poller Services and Reporting components have been migrated to .Net 6
• Platform Installer
  • Installs AspNetCore module when required
  • Allows export of platform certificate from database
    • Allows deletion of platform certificate from database
• Further strengthened the security of the WebApi code
• Strengthen security of platform by changing encryption and hashing method of all stored passwords
• Improved core compilers to use less memory
• Time zones are better handled on Linux and Docker platforms due to the migration to .Net 6
• Improvements in compression and handling of files attached to Tickets, Devices, Journals etc.
• Enabled compression on Web Api, Reporting Api and Polller Services for HTTPS

Breaking change in viewing Contact information

• Please give users "View Personal Data" permission to Contacts in order to allow them to view the  protected personal data part of the contact information

Breaking change in System Integration. Please read below information to successfully migrate to the new version:

• Due to new libraries being used in .Net 6, system integration that is configured to use Soap web services will stop working until the following steps are performed after updating to this version:
  • In the Administration / System / Integration page, view the Configuration for the affected Integration Profile
  • Under the Http Soap Api section, expand External Soap Web Services and for each defined Soap web service, regenerate the client code by clicking the "Generate Client Code" button
  • Validate and then save the configuration
  • Perform the above steps for all integration profiles that have Soap web services defined

Issues Fixed

• Fixed a null reference error when an unknown WebApi exception occurs
• Disabled browser prompting to remember password when editing passwords in a grid
• Fixed syling of some help pop-ups
• Fixed an issue with WatchDog processes for the LinuxAgent, LinuxPoller and LinuxGateway
• Fixed an issue with poller services having certification load issue
• Fixed an issue in the Connector application that was not allowing the user to select "Manual Login" if password vault credentials failed
• Fixed an issue in the Connector application whereby manually configured ports were not showing on connector popup in certain circumstances
• Fixed an issue in reporting that broke the forecast tables after migrating to monthly statistics tables
• Fixed an issue in Api polling whereby in some circumstances a timeout during the Api authentication would stop further authentication retries
• Fixed an issue in the poller whereby Tcp connection monitoring caused the poller to crash when the Tcp connection failed in certain circumstances
• Fixed an issue whereby the adminstrator could not assign access control to Owner security principal type
• Fixed an issue in the Api Definitions whereby the Api entity definition parent wasn't setting value
• Fixed an issue in the Api Access Profiles relating to protocol state of "device direct" monitored Apis
• Fixed typo in Web Api method name causing an error when rejecting a Change Ticket

​

Patch Releases

There are no patch releases available for this version.