<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=1110556&amp;fmt=gif">
August 10, 2021

Automated Remediation #5: Getting Started

by: Paul Weschler

Once your team is ready to move forward with its automated remediation efforts, you’ll need to establish the required elements. In the following sections, we detail those requirements, offer an estimated level of effort, and then describe the key user stories that are involved.


  • Licenses (see sidebar):
    • AIOps, specifically the DX Operational Intelligence solution
    • Automic Automation
  • AIOps (DX Operational Intelligence) is provisioned in SaaS
  • Automic Automation is provisioned. SaaS implementation is recommended. However, an on-premises option is also available, which will need additional configurations.
  • Optional. A basic set of enterprise-specific automations, such as jobs and workflows. Not required if focusing solely on automated remediation, which is a very good initial use case.
  • Data sources connected to AIOps
  • Optional. Business service defined in AIOps that encapsulates infrastructure the automation actions will act on.

Why it Pays to PLA

Broadcom offers customers the opportunity to sign on for Portfolio License Agreements (PLA). PLAs are unique software licensing options that enable enterprise customers to gain maximum value from the adoption and usage of solutions in the Broadcom Enterprise Software Division (ESD) portfolio. Through PLAs, customers can realize a range of significant benefits, including improved budgetary predictability, reduced costs, simpler pricing structures and procurement efforts, and unlimited solution access.

To learn more, see the IDC Report entitled “Broadcom Creates Portfolio License Agreement to Accelerate Enterprise Transformation and Modernization with Digital Infrastructure Software.”


Anticipated Level of Effort

Within many organizations, establishing automated remediation can take approximately four weeks, comprising two, two-week sprints. However, a number of factors can affect an organization’s potential timelines. For example, teams that have existing automated actions that can be used on target systems and services can see this time and effort reduced. To learn more about the estimated scope of effort required in your organization, connect with your account representative.

Key User Stories

With the requirements above met, teams will then need to complete the following high-level stories. Depending on the scope, timeframes, and target outcomes that your team established, it may be helpful to break these stories down into smaller efforts.

Story Title Story Description Size
Identify business service or system With the assistance of a business owner or champion, identify a business service, or an associated system. The system should be a supported data source that has components that can generate event, alarm, or metric data. Ideally, the data source is already connected to AIOps, and Automic Automation Agents are configured to perform actions on the infrastructure. Small
Automated Remediation    
Verify AIOps platform Verify that the AIOps platform is properly installed, with user roles configured. Small (SaaS)
Medium (on-premises)
Integrate data sources to AIOps (if needed) If not already completed, integrate initial data sources with AIOps. These should be event or alarm data sources that are related to the components of the target business service. Validate that events or alarms are received for the components that will form the business service. Medium
Create a business service (if needed) Create one business service in the AIOps Service Analytics module that contains the monitored elements. Small
Verify Automic Automation platform Verify that the Automic Automation platform is properly installed, with user roles configured. Small
Configure Automic Automation agents (if needed) If not already completed, configure OS agents and other Automic Automation agents for executing actions on the infrastructure that will be used. Medium
Integrate AIOps and Automic Automation Configure AIOps channel integration with Automic Automation, and verify it is functioning correctly. Medium
Analyze and design candidate actions Review alarms generated by the business service or system, interview operators and system administrators, and identify common actions that resolve alarms. Evaluate if Automic Automation can automate those actions. Small to Medium
Develop the first automation actions Create initial automations, either from scratch or by leveraging action packs from the Automic Automation Marketplace. Medium [Suggestion: time box these stories]
Demonstrate automated remediation Create a condition in which an alarm is triggered in AIOps, and an operator may select a pre-defined automation action that will resolve the alarm. Small
Iterate and improve actions Populate the backlog with user stories for iteratively improving and adding additional automations. Small
Document methodology of developing automations Write a brief document with the methodology for creating additional actions. Medium


For More Information

To learn more, be sure to browse the links below, which feature lists of educational videos: