The only way to make the transition is to put some capabilities in place to automate a lot of the grunt work that must get done to resolve today's problems. For example, attempting to recreate a Web application problem in a test lab is a time-consuming effort that usually fails. Investing in a solution that captures the problematic transactions directly from the production environment saves time doing this. Another example is augmenting an existing rules-based correlation engine with a product that automatically baselines performance and creates alarms only when behavior is abnormal. Not only will the number of alarms decline (staff will spend less time clearing nuisance alerts), but staff will also spend less time writing basic correlation rules in general.
The key with this approach is that the capabilities must slide into your existing management environment without requiring a lot of staff training and integration effort or integration maintenance. Haphazardly bolting together different products for each capability is a recipe for disaster in terms of maintaining the integration. Successfully climbing out the reactive management hole requires that each capability is selected for its time-saving value but implemented with integration and reuse in mind.
Dig Deeper on Software Performance Management
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.