US2015012635A1PendingUtilityA1

Systems and methods for organic knowledge base runbook automation

Assignee: MONOLITH TECHNOLOGY SERVICES INCPriority: May 26, 2011Filed: May 5, 2014Published: Jan 8, 2015
Est. expiryMay 26, 2031(~4.8 yrs left)· nominal 20-yr term from priority
G06N 5/02H04L 41/00
35
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

The present invention is directed towards systems and methods for automating runbook documentation. The method according to one embodiment of the present invention comprises receiving a network event and determining whether the event is a known or unknown event. The method comprises executing a policy associated with the event if the event is known event. The method comprises passing the event to the operator for review against a database of existing runbooks if the event is an unknown event. The method comprises executing an existing policy if the operator identifies a runbook for the runbook event. The method comprises requesting a new policy for the event if the operator does not identify an existing runbook for the event.

Claims

exact text as granted — not AI-modified
1 - 20 . (canceled) 
     
     
         21 . A system for automating runbook documentation for unknown events based on known events, the system comprising:
 a data storage device operative to store runbooks associated with known events;   a processing device operative to: receive selections of the runbooks to execute for an unknown event, provide execution results of policies referenced by the selected runbooks for the unknown event, re-evaluate the policies for the unknown event based on the execution results, associate the unknown event with the selected runbook, and store the association between the unknown event and the selected runbook in the data storage device; and   a policy engine operative to subsequently execute policies referenced by the runbooks for the unknown event based on the association of the unknown events with the selected runbooks.   
     
     
         22 . The system of  claim 21  wherein the policy engine is operative to automatically execute policies for a known event. 
     
     
         23 . The system of  claim 21  wherein the policy engine is operative to execute a policy for a known event in response to a request from a network operator. 
     
     
         24 . The system of  claim 21  wherein the data storage device is operative to store runbooks in response to a request from a network operator for a creation of a new runbook for an unknown event. 
     
     
         25 . The system of  claim 24  wherein the new runbook is created by a network administrator. 
     
     
         26 . The system of  claim 21  wherein the data storage device is operative to be searched by a network operator for an existing runbook. 
     
     
         27 . The system of  claim 21  comprising at least one network operator workstation and at least one network administrator workstation communicatively coupled to the data storage device. 
     
     
         28 . A method for automating runbook documentation for unknown events based on known events, the method comprising:
 receiving an unknown network event;   receiving selection of one or more runbooks to execute for the unknown event;   executing one or more policies associated with the selected runbooks;   providing execution results of the policies referenced by the selected runbooks for the unknown event;   re-evaluating the policies for the unknown event based on the execution results, associate the unknown event with the selected runbook,   storing the association between the unknown event and the selected runbook; and   requesting a new policy for the unknown event if an existing runbook is not selected to execute for the unknown event.   
     
     
         29 . The method of  claim 28  wherein executing a policy occurs automatically. 
     
     
         30 . The method of  claim 28  wherein executing a policy occurs in response to a request from a network operator. 
     
     
         31 . The method of  claim 28 , comprising storing runbooks in response to a request from a network operator for a creation of a new runbook for an unknown event. 
     
     
         32 . The method of  claim 31 , wherein the new runbook is created by a network administrator. 
     
     
         33 . The method of  claim 28 , comprising associating existing runbooks with unknown events. 
     
     
         34 . Non-transitory computer readable media comprising program code for execution by a programmable processor that instructs the processor to perform a method for automating runbook documentation for unknown events, based on known events, the computer readable media comprising:
 program code for receiving an unknown network event;   program code for receiving selection of one or more runbooks to execute for the unknown event;   program code for providing execution results of policies referenced by the selected runbooks for the unknown event;   program code for re-evaluating the policies for the unknown event based on the execution results, associate the unknown event with the selected runbook,   program code for storing the association between the unknown event and the selected runbook; and   program code for requesting a new policy for the unknown event if an existing runbook is not selected to execute for the unknown event.   
     
     
         35 . The computer readable media of  claim 34  wherein executing a policy occurs automatically. 
     
     
         36 . The computer readable media of  claim 34  wherein executing a policy occurs in response to a request from a network operator. 
     
     
         37 . The computer readable media of  claim 34 , comprising program code for storing runbooks in response to a request from a network operator. 
     
     
         38 . The computer readable media of  claim 37 , wherein the new runbook is created by a network administrator.

Join the waitlist — get patent alerts

Track US2015012635A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.