Date: December 2015
JetPatch version 3.0 includes these new features:
- Operational Compliance Console (Beta)
Operational Compliance Console (Beta)
JetPatch 3.0 offers a new policy engine and a new console for tracking and acting on the health and configuration of management tools and services.
The new engine can detect a wide range of operational compliance issues, such as:
- Missing required management tools & services
- Forbidden management tools being deployed
- Mis-configured tools (e.g. wrong agent configuration, mis-configured on the back-end side, or reporting to the wrong back-end)
- Agents being down or experiencing health and stability issues
Policies can now detect issues not just with JetPatch-managed tools, but also with any other server management tools discovered by querying their back-end side. Therefore even before deploying JetPatch management services in a new environment, users can still get valuable insight on the state of their pre-existing set of management tools.
From a users point of view, any compliance issue detected by the policy engine is recorded as an exception, and the entire list of current and past exceptions is accessible and search-able through the new user console.
JetPatch 3.0 features the new operational compliance console in Beta mode, and subsequent versions will enhance and improve it according to customer feedback.
- Extend the ability to define negative policy rules that disallow management services on groups of servers
- API key's will now only be visible at creation time
- The ability to tag multiple servers using an external CSV file has been added. The CSV format is as follows where the TagName is mandatory: TagName,ServerName,HostName,IP
- Management tools that fail on the endpoints now have a new icon representing that the agent has failed -
- Health script notifications can now be seen under the vAgent column facet as "Alerted"
- The create policy rule window has been redefined to match the new operational compliance feature including the following new enhancements:
1. Policy rule name
2. Severity of the exception
3. Enable/Disable the rule
4. Automatically fix exceptions
5. Retry behavior of automatic fixing of the exceptions
The new operational compliance feature entails a complete rewrite of the policy engine used to define and enforce operational compliance rules. As a result of this rewrite, upgrading from 2.x to 3.0 will remove all existing policy rules. Therefore, if you have rules defined in 2.x, you should document them and re-define them in JetPatch after the upgrade.