Skip to main content
Answer

Difference between Runbook based TAF and NI based TAF?

  • January 25, 2023
  • 1 reply
  • 135 views
pradeep.gaddameedi
Forum|alt.badge.img

What are the major differences between Runbook based TAF and NI based TAF? Explain which is the best approach on what kind of scenarios? 

Best answer by Venkatesh Ravikanti

 

Hi Pradeep,

Please find below differences between TAF v2 & v3

Triggered Automation Framework Version2

Triggered Automation Framework Version3

Run book based triggered Automation framework.

Intent based triggered automation framework

 

Runbooks with automation assets [DVT, Q App etc] can be triggered from ITSM tool

Intents / intent cluster / intent Templates can be triggered from email, MS teams chatbot, ITSM /Service Now.

Configuration workflow

  • Download and install NetBrain connecter v2 from SNOW App store.
  • Configure NetBrain connector in SNOW [ Key parameters – Endpoint, Authentication, Tenant, Domain ID]
  • Configure Shared Data field in SNOW to define what incident fields should be sent to NetBrain during event trigger.
  • Configure Automation template and trigger rule to define when and how to trigger NetBrain during an event/incident
  • Configure API Stub and API Trigger template in NetBrain to filter incoming incidents and trigger required Run Books and dynamic maps.

Configuration workflow

  • Download and Install NetBrain connecter v3 from SNOW App store.
  • Configure NetBrain connector in SNOW [ Key parameters – Endpoint, Authentication, Tenant, Domain ID]
  • Configure Shared Data field in SNOW to define what incident fields should be sent to NetBrain during event trigger.
  • Configure Trigger rule in Service now with condition to trigger NetBrain. [Ex: short_desc contains “VPN Down”]
  • Configure “Incoming incident type” to filter incoming incidents. [key parameters to configure – Source, filter condition]
  • Associate the incident type with network intent / intent cluster / Intent template so that filtered incoming incidents will trigger network intents.

 

         

 

 

 
  • This triggered automation will execute on the live data pulled as there is no baseline in the automation assets in this TAF version.
  • Automation assets that are built part of runbook requires no code or low code.
  • Network intents have baseline hence we can perform comparison between current [live data] and baseline in this TAF version.
  • No Coding knowledge is required to build Network Intents and TAF v3
  • In this TAF version Users can interactively execute the runbooks once the diagnosis and map are triggered by an event.
celina.chan
P

1 reply

V

 

Hi Pradeep,

Please find below differences between TAF v2 & v3

Triggered Automation Framework Version2

Triggered Automation Framework Version3

Run book based triggered Automation framework.

Intent based triggered automation framework

 

Runbooks with automation assets [DVT, Q App etc] can be triggered from ITSM tool

Intents / intent cluster / intent Templates can be triggered from email, MS teams chatbot, ITSM /Service Now.

Configuration workflow

  • Download and install NetBrain connecter v2 from SNOW App store.
  • Configure NetBrain connector in SNOW [ Key parameters – Endpoint, Authentication, Tenant, Domain ID]
  • Configure Shared Data field in SNOW to define what incident fields should be sent to NetBrain during event trigger.
  • Configure Automation template and trigger rule to define when and how to trigger NetBrain during an event/incident
  • Configure API Stub and API Trigger template in NetBrain to filter incoming incidents and trigger required Run Books and dynamic maps.

Configuration workflow

  • Download and Install NetBrain connecter v3 from SNOW App store.
  • Configure NetBrain connector in SNOW [ Key parameters – Endpoint, Authentication, Tenant, Domain ID]
  • Configure Shared Data field in SNOW to define what incident fields should be sent to NetBrain during event trigger.
  • Configure Trigger rule in Service now with condition to trigger NetBrain. [Ex: short_desc contains “VPN Down”]
  • Configure “Incoming incident type” to filter incoming incidents. [key parameters to configure – Source, filter condition]
  • Associate the incident type with network intent / intent cluster / Intent template so that filtered incoming incidents will trigger network intents.

 

         

 

 

 
  • This triggered automation will execute on the live data pulled as there is no baseline in the automation assets in this TAF version.
  • Automation assets that are built part of runbook requires no code or low code.
  • Network intents have baseline hence we can perform comparison between current [live data] and baseline in this TAF version.
  • No Coding knowledge is required to build Network Intents and TAF v3
  • In this TAF version Users can interactively execute the runbooks once the diagnosis and map are triggered by an event.
pradeep.gaddameedi
prallu
K

Follow NetBrain on LinkedIn

Terms & ConditionsCookie settingsAccessibility statement