DX Application Performance Management

 View Only

Blog Challenge #2: Learning a New Application Monitoring Solution Architecture

By Hallett German posted Sep 20, 2017 03:39 PM

  

Introduction

I am trying to write as many blogs as I can this week to reduce my "to-do blog topic inventory." Today, I cover learning a new solution architecture. 

It is a followup to my 2014 blog -- It's the Architecture, Silly! 

 

First step: Get an Overview

 

Review both a high-level and detailed solution architecture diagram and see what major components are involved. If you can, determine the high-level workflow of a "transaction/event".

 

Understand the basic and advanced functions of each solution component. Which functions/components are enabled by default?

 

Review official docs/training/user communities for a "real world" understanding of the solution architecture.

 

Understand capacity limits and what configuration settings/hardware are recommended for an optimized environment.

 

Second Step: Prepare to Dive Deeper

 

Determine the function/workflow combination of the solution.

For example, if you learn that only one component directly monitors network traffic, then you now know not to look there for end-user reporting export problems.

 

Create Knowledge Documents/Troubleshooting Guides based on these insights.

 

Third Step: Getting to a Deployment-Ready Architecture

 

Learn what a steady state for a solution looks like including a healthy monitoring component log. Review known issues and fixed bugs for a particular release

 

Fourth Step: Optimize/Maintain Your Architecture

As I stated before, Solution Architectures should be reviewed two-four times a year. Optimization of hardware/software is key, especially in a fast changing environment.  Review documentation, blogs, etc. on optimization/maintenance including capacity planning for your next architectural upgrade.

 

Your Turn:
Was this a good topic to cover? Are you using an approach like the above or something else? Please share your experiences! 

0 comments
0 views

Permalink