DX UIM 23.4: Improved Zero-Touch Monitoring, Updated MCS Architecture

The Monitoring Configuration Service (MCS), under continued innovation since 2017, is a feature for DX UIM that helps solution administrators expedite device configuration and alarm policy deployment for the most popular monitoring technologies.

The release of DX UIM 23.4 offers enhanced workflows for using MCS to do both local and remote monitoring. The enhancements include template and profile management, improved scalability and reliability, best practices for self-monitoring of MCS, and in-context MCS dashboards. In this post, I’ll outline why you should upgrade now for the improvements to MCS, in addition to other updates available in DX UIM 23.4.

As one service provider customer based in Asia noted, "DX UIM 23.4's improved scale and resilience for MCS is exactly what we needed. Deploying monitoring profiles has never been smoother or more reliable."

MCS is used to make monitoring more seamless through a zero-touch approach to configuration and alarm policy deployment. In a scenario in which thousands of devices are to be monitored, MCS can execute the following tasks:

• Based on group configuration, devices are assigned to individual groups, with each group having thousands of devices.
• Configuration Profiles in MCS are created as a centralized way of defining the configuration, what needs to be monitored, and which metrics to collect. In this way, there is only one process (MCS) that maintains the configuration, and the configuration changes are tracked more effectively.
• Once created, profiles are applied to thousands of devices in the group, reaching all devices more seamlessly.
• Even the updates made to group-level profiles are propagated to devices and configurations, making updates easier to execute than with traditional configuration methodologies.
• As a device moves in and out of a particular group, the configurations are automatically applied as per configuration profiles present in the groups.
• The thresholds on metrics can be configured at centralized locations using ”alarm policies” in the Operator Console.

To learn more, access the Monitoring Configuration Service: Customer Adoption Guide.