|By Larry Dragich||
|October 27, 2014 02:45 PM EDT||
Your Next Move During an IT Postmortem Review
Can a postmortem review help foster a curiosity for innovative possibilities to make application performance better? Blue-sky thinkers may not want to deal with the myriad of details on how to manage the events being generated operationally, but could learn something from this exercise.
Consider the major system failures in your organization over the last 12 to 18 months. What if you had a system or process in place to capture those failures and mitigate them from a proactive standpoint preventing them from reoccurring? How much better off would you be if you could avoid the proverbial "Groundhog Day" with system outages?
The argument that system monitoring is just a nice to have, and not really a core requirement for operational readiness, dissipates quickly when a critical application goes down with no warning.
Starting with the Event and Incident Management processes may seem like a reactive approach when implementing an Application Performance Management (APM) solution, but is it really? If "Rome is burning", wouldn't the most prudent action be to extinguish the fire, then come up with a proactive approach for prevention? Managing the operational noise can calm the environment allowing you to focus on more of the strategic aspects of your business.
Asking the right questions during a postmortem review will help generate dialog, outlining options for alerting and prevention. This will direct your thinking towards a new horizon of continual improvement that will help galvanize proactive monitoring as an operational requirement. The areas to focus your questions on should correlate to the Reactive, Proactive and Predictive mindsets. For further insight, click here to read the 3 questions that you can use that build on each other.
[This article first appeared in APM Digest almost a year ago and has been re-posted on LinkedIn. The general concepts still hold true when considering 3 simple steps for continual service improvement.]
Jul. 29, 2015 04:30 PM EDT Reads: 496
Jul. 29, 2015 04:15 PM EDT Reads: 317
Jul. 29, 2015 04:00 PM EDT Reads: 1,063
Jul. 29, 2015 03:15 PM EDT Reads: 366
Jul. 29, 2015 03:15 PM EDT Reads: 230
Jul. 29, 2015 03:00 PM EDT Reads: 464
Jul. 29, 2015 03:00 PM EDT Reads: 1,251
Jul. 29, 2015 02:30 PM EDT Reads: 318
Jul. 29, 2015 02:30 PM EDT
Jul. 29, 2015 02:17 PM EDT
Jul. 29, 2015 02:00 PM EDT Reads: 332
Jul. 29, 2015 02:00 PM EDT Reads: 1,164
Jul. 29, 2015 01:45 PM EDT Reads: 417
Jul. 29, 2015 01:00 PM EDT Reads: 1,056
Jul. 29, 2015 01:00 PM EDT Reads: 1,944