Instance Controller release 2.1.0 announcement

Instance Controller

We have a great announcement for you about the new Instance Controller release, with the number 2.1.0. Together with the development team, our Architect spent many hours bringing our customers new features and some defect fixes in the Instance Controller solution during the last few months

This release focuses on improvement, and new features in areas of Cloning, Backup, Monitoring Engine, and Orchestration, Reconciliation and Core of the application received new features and fixes. From the list of brand-new features, we would like to highlight "Infrastructure users", "Predictive Anomaly Detection", "Automated instance decommissioning", "Configuration sets for datacenters", and "Retention period for backups"

We have a bunch of ideas on how to improve the solution. Still, we are first listening to our customers, who help us discover new areas of improvement based on their experience and needs while using the solution. This feedback is extremely important for us, and many thanks for that. Also, in this release, we are covering some of the ideas from our customers.

Instance Controller

We would like to highlight the following new features and defect fixes:

  • DB socket and defaults file - Enables connection based on user decision via host IP and port or socket file when the connection is made locally—enhancing security depending on OS and security settings
  • Automated instance decommissioning - Decommission can be done easily ordered and executed
  • Customer filtering in CWC portal - It is possible to filter instances on the portal by customer
  • Predictive anomaly detection - Anomaly detection is based on standard system performance flow, where the system compares the past with the present and thus can detect anomalies
  • Configuration sets for Datacenters - Different configuration settings are enabled by defining "groups of configurations". When defining a new instance, a specific group of the configuration can be taken. Depending on the group, the behaviour and deployment approach differs
  • Infrastructure user - On-demand user creation to ServiceNow infrastructure servers (application nodes, database servers)
  • The retention period for backups - Enable to schedule deletion of old backups automatically
  • List of available backups - Display list of backups stored on the server storage
  • Monitoring long-running transactions – Enable monitoring of long-running transactions so that performance issues can be addressed
  • Monitoring integration into external ticketing system - This feature creates an incident on 3rd party system utilizing REST requests when a specific parameter breaches the defined threshold
  • Synthetic user State - Additional attribute "State" added into the Synthetic user record with states Requested, Active, Inactive, Error
  • Manual or automatic conditional node restart - Manual node ad hoc restart from Controller enabled. Reconciliation task ready to be enabled to restart node when specific node conditions are met
  • Verification page before cloning to show details of cloning procedure – Before cloning starts, the user can verify details of planned cloning procedure to limit starting of cloning procedure with incorrect settings
  • Many other small enhancements and fixes in areas of cloning, monitoring and orchestration