Closed-Loop Automation FAQs

CLA brings you a step closer to achieving a complete IBN system. A sturdy IBN solution needs the following elements:

  • Simple graphical user-interface to define business intent – declaratively and properly
  • A monitoring solution that constantly collects data from network resources
  • A CLA solution that verifies collected data with the desired network state and automatically resolves non-compliance

Yes, NOC teams can use Anuta ATOM in multiple ways to troubleshoot an issue. Once they get notified about an alert, they can start with the alert dashboard, derive insights from relevant charts, and use configuration and compliance management to verify any obvious issues as a manual process or utilize ATOM’s closed-loop automation and workflow automation to diagnose the issue and perform auto-remediation or auto-ticketing to ITSM tools

Every business requirement is unique and therefore every network has to be configured differently. However, we do offer some of the best known scenarios out-of-box in ATOM. Customers can use them or can create your own scenarios due to the flexible framework ATOM has.

ATOM supports email, slack notifications, or workflow as the action to an alert. These actions can be set for all the alerts or filtered alerts based on the use case. For example, all the alerts for a particular region can be routed to a particular slack channel. Or a specific alert type such as interface flapping, can be routed to a workflow to raise an incident ticket.

In the NetOps scenario, there is always an action that needs to be taken on breach of a KPI threshold. This action can be about raising an incident ticket or performing a diagnosis or performing a remediation. This aspect of NetOps can be automated using ATOM’s workflow automation. The workflows can be created for address any of the above-mentioned issue and will get triggered. For example, a diagnosis workflow for a well known issue, will log into the devices involved, take all the command snapshots and raise or update an incident ticket attaching this information.

Very complex alerting scenarios, where multiple KPI breaches can result in network degradation can be easily handled using workflows. Using workflows, ATOM can correlate between these different scenarios and update the alert with meaningful information.

  • Alert definition to handle complex KPIs and its thresholds
  • Alert history to handle multiple occurrences by avoiding unnecessary noise
  • Alert deduplication to ensure no similar alerts are shown at the same time
  • Auto-ticketing
  • Event correlation
  • Event enrichment
  • Manual and Automated actions

Yes,  ATOM allows baseline to be defined using performance data collected through SNMP, SNMP Trap, Syslog or Telemetry, and appropriate actions can be associated – Email, Slack, Workflow Actions for remediation or end-user intervention through ITSM tools such as Jira, ServiceNow etc.