The APM team is busy at work on a number of highly requested enhancements:
- Scalability and Performance Enhancements
- Dynamic Service Level Groups
- Ability to select multiple Orion objects (statically or using a dynamic query) even of different types (e.g. nodes, interfaces, applications, groups) and group them into a container that can be used to visualize status and for configuring "service level" alerts
- Ability to see Groups at the summary and details view levels
- Ability to set Group level status as worst (worst status rolls up), mixed (yellow unless all objects are green, or all or red), or best (best status rolls up for high avail/hot backup scenarios)
- Ability to alert on Group status
- Basic Root Cause Analysis (based on Group concept above)
- Ease of Deployment Enhancements
- FIPS compatibility
- Ability to run on a Windows system with the FIPS GPO enabled
- VMware infrastructure monitoring
- Visibility into the vCenter, DataCenter, and Cluster levels (in addition to ESX host and VM guest visibility already provided)
- New VMWare component monitor providing the ability to monitor almost any statistic available via the VMWare API.
- Ability to change the namespace used to pull counters in WMI monitor (i.e. allow selection of more than just CIMv2)
- Ability to include applications in calculation of node child status. So if node is up, but application on that device is down, you will see status child status icon indicating there is a problem.
- Ability to install APM on a separate database from NPM and run in "standalone" mode
- RPC alternative to WMI for Windows Services performance counters.
PLEASE NOTE: We are working on these items based on this priority order, but this is NOT a commitment that all of these enhancements will make the next release. We are working on a number of other smaller features in parallel. If you have comments or questions on any of these items (e.g. how would it work?) or would like to be included in a preview demo, please let us know!