Self-Enabled Well being Monitoring of NSO Community Providers

A community service is simply nearly as good as its well being. Therefore, it’s essential that end-to-end administration of community providers ought to embody well being monitoring as a part of the community service life cycle. After we discuss automating a community service, we imply automating the provisioning and upkeep of a community service. Well being monitoring of a community service is often regarded as a separate operation that’s added after the community service is provisioned. Well being monitoring is usually carried out via scripts or via UI. If the scope of the community service adjustments, then the well being monitoring of the modified service have to be revised as effectively. These disjointed operations can lead to:

• Overhead for provisioning of well being monitoring of the community service.
• Upkeep overhead when the community service is modified.
• Enhance in operational bills on account of further assets required for provisioning and upkeep for well being monitoring.

Well being monitoring with Cisco Crosswork

Cisco Crosswork permits the well being monitoring to be constructed as an integral a part of the NSO community service, permitting auto figuring out the well being monitoring KPI’s and provisioning of the KPI’s for the NSO community service. That is completed by defining one NSO community service for well being monitoring, which is run every time a brand new NSO community service is provisioned. The benefits of enabling well being monitoring of NSO providers embody:

• Auto detection: The KPI’s for the community service are auto detected and provisioned primarily based on the community service being commissioned.
• Reusability: Outline the well being monitoring NSO service as soon as and reuse it for all NSO providers.
• Improved Operational Effectivity: removes the necessity for manually configuring and sustaining the well being monitoring KPIs for every of the community providers.

Auto enabling and monitoring of KPI’s

Cisco’s Crosswork Well being Insights, Change Automation, and Community Providers Orchestrator (NSO) functions are used to realize the objective of auto enabling and monitoring of KPI’s on NSO providers.

• Cisco Crosswork Well being Insights allows defining the best set of KPI’s to handle all objects of the community service, permitting customization of KPI thresholds, monitoring the KPI’s and elevating alerts if the thresholds are exceeded. These KPI’s could be enabled as a part of service provisioning utilizing NSO, thus monitoring the well being of the community service from the time it’s commissioned.
• Crosswork Change Automation does closed-loop automation utilizing playbooks. Playbooks use NSO to configure the community to repair the problems associated to the KPI alerts. KPI’s are mapped to playbooks, even earlier than the KPI thresholds are exceeded. This helps to invoke the playbook simply if the edge is exceeded. Invoking the playbook turns into environment friendly and quick as it may well derive the inputs to the playbook from the KPI alert, and playbooks leverage the NSO capabilities.
• Community Providers Orchestrator (NSO), the orchestrator utilized by Crosswork Change Automation for provisioning community providers.

Determine 1 reveals the interactions of the Crosswork Functions for auto detecting and enabling KPI’s for well being monitoring of a community service.

Determine 1: Auto Enabling Well being Monitoring of Community Providers

An NSO service is imported into Crosswork Change Automation as a play. Then performs could be mixed to kind a playbook. The ordering of performs in a playbook defines the sequence of execution of the performs. When an NSO community service is to be deployed, and well being monitoring is to be enabled on the community service, the NSO service to be deployed is imported into Crosswork Change Automation as a play right into a playbook and the well being monitoring NSO service can also be added as a play to the identical playbook. Determine 1 reveals the workflow steps for deployment of the playbook.

Step 1: When the playbook is executed, the NSO service is deployed first. As soon as the service is efficiently deployed, the well being monitoring service is activated.

Step 2: The well being monitoring service takes the NSO service as an enter. This service robotically generates an inventory of KPI’s related to the NSO service primarily based on the configuration of the NSO service. The well being monitoring service then calls the Crosswork Well being Insights to create a KPI profile consisting of related KPI’s.

Step 3: Crosswork Well being Insights calls NSO to provision the KPIs of the KPI Profile on the endpoints of the NSO service. From this level onwards the well being of the NSO service is monitored towards the thresholds of KPI’s. If any of the thresholds are exceeded, Crosswork Well being Insights generates alerts.

See it in motion with this demo.

The code for the use case

Associated assets

We’d love to listen to what you suppose. Ask a query or depart a remark beneath.
And keep linked with Cisco DevNet on social!

LinkedIn | Twitter @CiscoDevNet | Fb |  Developer Video Channel

Share: