Customers are increasingly relying upon your applications for their daily lives. From general information to shopping to travel, your customers view applications as critical to their daily lives. They demand that the applications work, correctly and quickly, the first time - every time. Applications have become more and more complex, often cloud-based, and updated repeatedly. How will you make sure your applications are ready for today’s demanding users? This session will cover a typical customer experience, proving how critical today’s modern applications have become. This will highlight the growing importance of monitoring dynamic environments in our constantly changing, modern world.
Develop KPI model
Gather metrics & document current state
Compare to baseline after change
Allows you to understand what “normal” looks like
Helps systematically determine when things go sideways
Identifying baselines involves determining the type of metrics you want to measure, and understanding why you want to measure them.
Measuring your key metrics before a change allows you to use these metrics during the change.
To do this, we use a KPI model.
KPIs stand for Key Performance Metrics.
They are the important metrics that you need to track during your migration in order to assure your migration is successful.
Typically, you’ll have technical KPIs that refer to the underpinnings of how your application works.
You have User Experiential KPIs, which deal with how your customers see and experience your site.
And you have Business KPIs, which describe how the performance of your application is impacting your business requirements.
KPIs stand for Key Performance Metrics.
They are the important metrics that you need to track during your migration in order to assure your migration is successful.
Typically, you’ll have technical KPIs that refer to the underpinnings of how your application works.
You have User Experiential KPIs, which deal with how your customers see and experience your site.
And you have Business KPIs, which describe how the performance of your application is impacting your business requirements.
KPIs stand for Key Performance Metrics.
They are the important metrics that you need to track during your migration in order to assure your migration is successful.
Typically, you’ll have technical KPIs that refer to the underpinnings of how your application works.
You have User Experiential KPIs, which deal with how your customers see and experience your site.
And you have Business KPIs, which describe how the performance of your application is impacting your business requirements.
Here are some example KPIs from a fictional airline. Your KPIs will be different, and are dependent on your industry, company culture, and system requirements.
Whatever your KPIs are, determine them and start monitoring them *before* you begin your migration process.
Is your application running as expected in the cloud?
Is it using the resources you expect it to use?
Early instrumentation allows you to uncover issues and roadblocks easier and quicker.
{c} Is your app working? Is your application running as expected on the new infrastructure? ** Comparing your KPIs to your baselines gives you data to understand if your migration is going awry.
{c} Is your app running efficiently? Is it consuming the cloud resources it requires in an efficient and effective way?
KPIs stand for Key Performance Metrics.
They are the important metrics that you need to track during your migration in order to assure your migration is successful.
Typically, you’ll have technical KPIs that refer to the underpinnings of how your application works.
You have User Experiential KPIs, which deal with how your customers see and experience your site.
And you have Business KPIs, which describe how the performance of your application is impacting your business requirements.