Backwards Compatibility

  1. API Consumer Identity field’s value under Monitoring LOGS DETAILS tab will not be shown unless Sentinet Users have View Recording and Properties permission in their User Role. Previously, Consumer Identity is shown if Sentinet Users have View Logs permission in their User Role.

    Consumer Identity

  2. During Automated Deployment and Configuration, if Node with the Node Key defined in Node’s .INI file (or XML configuration file) does not exist in the Repository, then the Node will be automatically created by the scripts. Previously, scripts were generating error in this case and Node with the Node Key unknown to the Repository is not created. This change helps to implement “fresh” on-premises and cloud automated Sentinet deployments in the environments where Sentinet is installed along with its new Repository (and Monitoring if applicable) database(s).