Preventing the Next Deployment Issue with Continuous Performance Testing and Monitoring

Post on 11-May-2015

704 views 2 download

Tags:

description

Traditionally, identifying and remedying performance problems resulting from application deployments has been a slow, reactive process. Tools exist which report on application changes and problems after they occur, but how do you prevent your next performance issues before they even begins? Join Correlsense and dbMaestro for an online seminar outlining the crucial strategies for continuous performance testing and monitoring. We will discuss: -Limitations of traditional strategies for application deployments -Best practices for eliminating the risks of application changes -Solutions for proactive application performance monitoring and database change management

Transcript of Preventing the Next Deployment Issue with Continuous Performance Testing and Monitoring

Preventing the Next Deployment Issue with Continuous Performance Testing and Monitoring

December 13, 2012

Tom Batchelor, Correlsense

Uri Margalit, dbMaestro

Agenda1. History of APM2. Steps to Proactive Monitoring3. The Need for Joint APM/DCM4. Summary/Q&A

Housekeeping

• Presentation will last 30 minutes• Submit questions via the chat window• Slides will be made available tomorrow

Featured speakers

Tom BatchelorSenior Solutions ArchitectCorrelsense

Uri MargalitDirector of Product ManagementdbMaestro

HISTORY OF APM

In the beginning…

• End users would call IT/Help Desk• IT would try to simulate problem• No insight into end user experience

Evolution to on-demand traces

• Turn on in response to a problem• Doesn’t help us discover or predict problems• Still reliant on end users calling in

Evolution to 24x7 monitoring

• Capture end user data• See all tiers• Measure SLAs 24x7 for all users

But today’s solutions are still reactive!• How do you prevent performance issues before

they exist?

SRM Tools

Array Mgmt. SWSAN

Mgmt. SWServer

Mgmt. SWApplication

Performance SW

DatabaseServer

Storage Target

Lack end-to-end performance management view

“CPU and Memory are OK”

“PING works, Temp is OK”

“Plenty of Storage & No hardware failures”

“SAN has low utilization”

Application Server Fabric

X

“Plenty of capacity”

STEPS TO PROACTIVE MONITORING

Ticket closed

Topology map isolates the infrastructure components involvedTicket is escalated to right team

SLA Analysis points to the bottleneck area.

Proactive management- know before the users

shows the locations that are affected and user in apps

- detects degradation in SLA - Opens ticket

application team drills down Identifies faulty method

App/ops team provides workaround/fix. Change impact analysis proves issue has been resolved

Know what is slow

Understand your entire topology

• Auto-detected• Real-time• Without manual modeling

See the impact of changes in UAT

Compare performance over time

Track all requests through all hops

AppletApache

OC4JForms Runtime

Specific SQLs

• Track all user requests through all components (not just Java and .NET)

• Track a single end user across entire stack• Apache, OC4J, and Database

Track performance across geographies

Proactive monitoring benefits• Increase operational efficiency – Avoid application `brown-outs` and slowdowns – Reduce staff and time to resolution

• Save on hidden costs– Fix problems before they become really expensive– Solve problems in testing before going live

THE NEED FOR JOINT APM/DCM

Poll

• Which of these do you consider as the biggest benefit from Database Change Management?– Team Collaboration

– Change Policy Enforcement

– Development Process Management

– Merge & Deploy Automation

– Preventing Next Performance Issue

What is DCM?

• DCM – Database Change Management• Part of ALM (Application Lifecycle Management)

solutions• Foundation of Agile & CI

ContinuousIntegration

AutomatedDeployment

ConflictCode

Resolver

Business Req.

Integration

DCMDatabase

Code

SCMNativeCode

The database tier

• Database is major part of the application– Schema Structure

– PL/SQL Code

– Lookup Content

• Database is acentral resource

• Business data must be saved

Need for DCM

• Lack of order in database development• No visibility• “Out of Process” changes • Not having automated tasks• Problems in version releases• Responding slowly to changes in requirements

Benefits of DCM – development

• Database changes repository• Following SCM methods (Check-Out/Check-In)• All changes are documented• Control Who can do What, Where, When & Why

Benefits of DCM - deployment

• Integrated deployment engine• Business level audit• Roles & responsibilities enforcement

DCM & APM

There is enough time to redesign

Summary

• Today’s solutions are still reactive• Proactive monitoring strategies

mitigate the risk of change• dbMaestro and Correlsense offer

a joint solution for preventing thenext performance issue

Questions?

dbMaestro:www.dbmaestro.comPhone (US and Canada):+1-866-931-8855 Email: sales@dbmaestro.com

Correlsense:www.correlsense.comwww.correlsense.com/demoEmail: info@correlsense.com