Download - London Appdynamics User Group (LAUG) February 2013 Meetup Presented by IG

LONDON APPDYNAMICS USER GROUP | FEBRUARY 2013 | 1

London Appdynamics User Group (LAUG)February 2013 Meetup

Presented by IG


How AppDynamics isinfluencing our IT culture

Hamed SilataniAugusto Rodriguez


Contents

• Why is performance important to us?• How we measured performance historically• How AppDynamics is influencing positively:

Ð DevelopmentÐ ArchitectureÐ QAÐ Operations and Support

• Successes and challenges we found


IG’s context

• We offer Spread Betting and CFD trading

• Trading and price updates are time critical – Every millisecond counts

• Using AppDyanmics in production for 4 months


Development process

Proactive than reactive approach to performance:• Identifying latency issues in production is too late• Mostly on trading and charting platform

We try to improve the performance on each release

Res

pons

e tim

e


Development Process

Thinking about monitoring from the start• Influences how we design• It was expensive and focused

Ð Ad-hoc classes to wrap specific transactions and log metrics.Ð Creating custom metric collectors and graphing them.

• Not possible to have it everywhere


Development Process

Leave metric collection to its experts and focus on our business domain and differentiators.


Architecture


Architecture


QA

• Link Business Transactions to Services• Simpler option to sign-off architectural changes• Provide snapshots on bug reports when a service returns an error.


QA

• Helps with regression: Business transaction health view easily tells us: Ð What transactions are fundamentally brokenÐ Can’t tell if all transactions are OK


Operations & Support

Lower the bar to find performance issues• Easier to collaborate with other teams to solve the problem:

Ð focus on the solution.Ð With DBAs - > DB call times

• can pin point performance bottlenecks:Ð Bottlenecks caused by downstream componentsÐ Inefficient code in unfamiliar parts of the platformÐ Thread hogging calling a SAAS provider

• troubleshooting integration with 3rd party software.Ð Messaging broker



• BTs enables us to correlate exceptions across nodes



Ability to correlate events (cluster, nodes, etc).[gc , cpu]



Reduce the number of false positives alerts (Correlation of metrics for alerting).



Inventory of JVMs and config (* run reports on jvms)


Operational successes

• Datacenter failover

• Already used to improve our throughput


Operational challenges

• No way to promote config changes through environments

• Changes to BTs or metric names invalidates dashboards

• Invest in training to get the most out of it

• To get best of the tool work with Appd engineers


Going forward

• Doing end user monitoring (web and mobile)• Collect real-time business metrics and KPIs• Use events to mark application version changes• Diff flowmaps• Compare platform performance across all nodes between load tests


Q & A


THANK YOU!