Menu
▾
▴
DAWGPound
DAWG - Dynamic Advanced Workflow GUI
This is an exploration of more advanced ways of performing Fault Management sorts of things in Operations.
The current Event List methodology is the first problem. It is overwhelming people. But instead of cleaning up the events and the issues, folks sit and complain that its too many to respond to. Instead of working, they wait until a phone call happens.
Many operations environments are wholesale deleting events. Or the operations folks only respond to predetermined "actionable" events.
Did you ever think that a common event list is a 2 dimensional solution to a 4 dimensional problem? What do you work on first? What is causal and what is side effect? What is active? What is the state of the active? What custom er community is affected? Has a probable cause been determined? Who is doing what? Who is Responsible? Accountable? Consulted? Informed?
As a Manager,how do I look at a common event list and help organizeresourcesand priorities? How do I help?
In many cases, hundreds of hours are spent on formatting rules that are rarely seen. And when things change, it is incredibly difficult to trace through the rules to get the exact one fixed. And when it is fixed,how doyou test it?
The wiki uses Markdown syntax.
Project Members:
- Dougie!!! (admin)
Discussion
Requirements - Features
Facilitate Events, Alerts, and Alarms.
Event automation through triggers and stored procedures.
Front end in HTML5, angular.js, jquery.js, etc.
Provide for externally driven automation
Provide for internally driven automation
Historical event management
What if I used stored procedures to do the application flow from initial injection through to display?
Do the initial deduplication use INSERT OR DO logic. (Native to PG)
- Make sure the key is unique
- Could use a checksum or signature
The transition from event to alert to alarm to whatever could be done as stored procedures (You can use languages outside of SQL in PostgresQL.)
- Eliminates the "non-real time" associated with older event presentation tools.
- Enables the chaining of process. The implementer can decide when and where to display data.
- Data can be presented to multiple perspectives by processing the data where it makes sense.
Enrichment can be inline and a stored procedure.
- Could incorporate data like IP Addresses (v4and v6) in its various forms.
- Could use elements in JSON data. (PG has a native JSON data type)
- Data could be a view and as such, be dynamic.
Last edit: Dougie!!! 2016-02-03
Tiered displays Possibilities
**Alarms **
+- Alerts
+- Events
Or do something a bit unique like:
Tickets
+- Alarms
+- Alerts
+- Events
Or something like:
Responsible Org
+- Engineer
+- Ticket
+- Alarm
+- Alert
+- Event
Or something like:
Customer
+- Ticket
+- Location
+- Alarm
+- Alert
+- Event
A Workflow Based Interface versus an Event List
The NUMBER 1 problem with an Event List ...
**Folks just sit and stare.***
Why? Because it is confusing. What do they respond to first? What happens when you receive a new bunch and you're working on an event? What happens when the one youare looking at disappears?
One of the things that I REALLY LIKE about a KANBAN style workflow interface is that instinctively, it guides you to focus and finish tasks. You have a To Do column, an active Working list, and a done list. You want tograb things out of To Do, put them in Working, then, when done, you put them in Done.
Note, these could be arranged as Individual or Team work behaviors in that you could have individual tasks or team assigned tasks.
So,if you look at the KANBAN style interface,for presenting Alerts and Alarms:
You need an unassigned category - Be able to assign an event to a Team or accountable organization.
You need to capture alerts that are completed without assignment to an individual. Like an alert that com es in, then clears before it is worked.
You need to be able assign an event to more than one team. - Like an application problem that encompasses application engineers, storage, cloud, systems, and network. Let those teams and individuals declare Working and Done states yet not override the other teams.