For today’s IT operations teams, the stakes keep getting higher and demands only intensify. The services these teams are responsible for managing play an increasingly critical role in the prospects of the business, which means optimizing service levels is an absolute imperative. Meanwhile, the environments in play only seem to keep getting larger, more complex, and more dynamic.
Given these factors, monitoring is a task that keeps getting more vital and more difficult. To respond, operations teams must keep finding ways to boost their operational efficiency.
Introducing Monitoring Configuration Service
DX Unified Infrastructure Management (DX UIM) offers a range of features that help teams realize maximum efficiency in monitoring configuration, deployment, and administration. DX UIM Monitoring Configuration Service (MCS) represents an important capability that helps boost operational efficiency. With MCS, teams can significantly streamline monitoring administration in large-scale enterprise environments. Following are a few of the key features of MCS.
Bulk Administration
MCS enables administrators to create a set of configuration profiles that can be applied across thousands of devices.
Self-Service Capabilities
With MCS, teams can establish self-service capabilities, enabling end users to set up and run their own monitoring. This helps end users to get started faster and it reduces the workload for administrators. Plus, this self-service capability can be efficiently and safely employed across an organization. With DX UIM’s multi-tenancy capabilities, a single environment can support many different accounts, while ensuring individuals can only access the resources and data they’re authorized for.
Automation
Based on policies implemented, MCS can automatically deploy probes to target devices. For example, as devices are added to a group, monitoring can be automatically employed based on that group’s policies. Similarly, if a device is removed from a group, monitoring can automatically be decommissioned.
Dashboards
MCS features dashboards that enable teams to gain a fast understanding of the status of their deployments, groups created, and more. Dashboards can be customized to support a range of users and perspectives. Teams can categorize views by groups and profiles, and they can export data based on filters applied.
Deployer
Behind every template is a deployer, which denotes how data saved in a profile will be distributed. Typically, data is saved in a new section in a probe configuration file. (In the next post, I provide more details on key MCS components, including templates.) The deployer can execute a number of commands, including deploying logic and dictating how data saved in a profile should be handled.
Application Discovery
MCS features a template that enables application discovery. This template uses a unique deployer, which will deploy a script and a profile. These scripts can be run at any interval to determine whether a specific application is installed. For example, a script can check to see if MySQL is running. If so, it can then create a new attribute for a device, effectively defining the role as MySQL, and save that attribute to the database (Note, a device can have multiple roles, for example, if scripts identify multiple apps running.) In this way, teams can discover apps running and enable appropriate monitoring profiles to be deployed. (For more information on this topic, see my earlier blog post, “Application Discovery with DX Unified Infrastructure Management.”)
“For-Each” Feature
MCS offers a “For-Each” feature that enables teams to create profiles based on attribute values. These attribute values can be created as part of the app discovery process and through APIs. The number of profiles created is based on the number of attribute values. If one attribute value is detected, one profile will be created; if three values are found, three profiles will be created; and so on. (For more information on this feature, see my earlier blog post, “How to Use the For-Each Feature with DX Unified Infrastructure Management’s Monitoring Configuration Service.”)
How it Works
Following is a high-level overview of the process of employing MCS:
1. Create a Group
Administrators or users first create groups that devices will be added to. Groups contain filter criteria and profiles.
Teams can elect to create static or dynamic groups. Devices are assigned to static groups manually, or programmatically through APIs. When a new device is added to either group type, monitoring is employed automatically.
2. Create a Profile
To establish monitoring settings, teams define profiles.
3. Deploy the Profile
Once created, profiles are pushed to any devices that are associated with the group, and that meet the criteria specified in the template.
4. Manage Profile
Over time, administrators and users can create, modify, and delete profiles as needed to accommodate changing objectives and requirements.
5. Manage Group
Just as with profiles, groups will also be administered over time.
Conclusion
MCS offers a range of advanced capabilities that extend the power of DX UIM. With MCS, teams can do bulk administration of similar devices, dramatically streamlining both setup and ongoing administration. In Part 2, I take a look at the core elements that make up an MCS implementation.
Steve D'Arcy
Steve D’Arcy is one of Broadcom’s trusted advisors, learning about the challenges customers face and helping overcome them to ensure customers’ business goals are met. He has worked with unified infrastructure management since 2010, and during this time has collaborated closely with engineering and field operations to...
Other resources you might be interested in
This Halloween, the Scariest Monsters Are in Your Network
See how network observability can help you identify and tame the zombies, vampires, and werewolves lurking in your network infrastructure.
Your Root Cause Analysis is Flawed by Design
Discover the critical flaw in your troubleshooting approaches. Employ network observability to extend your visibility across the entire service delivery path.
Whose Fault Is It When the Cloud Fails? Does It Matter?
In today's interconnected environments, it is vital to gain visibility into networks you don't own, including internet and cloud provider infrastructures.
The Future of Network Configuration Management is Unified, Not Uncertain
Read this post and discover how Broadcom is breathing new life into the trusted Voyence NCM, making it a core part of its unified observability platform.
Rally Office Hours: October 9, 2025
Discover Rally's new AI-powered Team Health Widget for flow metrics and drill-downs on feature charts. Plus, get updates on WIP limits and future enhancements.
AAI - Navigating the Interface and Refining Data Views
This course introduces you to AAI’s interface and shows you how to navigate efficiently, work with tables, and refine large datasets using search and filter tools.
Rally Office Hours: October 16, 2025
Rally's new AI-driven feature automates artifact breakdown - transforming features into stories or stories into tasks - saving time and ensuring consistency.
What’s New in Network Observability for Fall 2025
Discover how the Fall 2025 release of Network Observability by Broadcom introduces powerful new capabilities, elevating your insights and automation.
Modernizing Monitoring in a Converged IT-OT Landscape
The energy sector is shifting, driven by rapid grid modernization and the convergence of IT and OT networks. Traditional monitoring tools fall short.