transactional monitoring for loosely coupled service architectures

37
@dkhan Transactional monitoring for loosely coupled service architectures Daniel Khan Node.js Technology Lead

Upload: daniel-khan

Post on 18-Jan-2017

263 views

Category:

Internet


0 download

TRANSCRIPT

Page 1: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Transactional monitoring for loosely coupled service architectures Daniel KhanNode.js Technology Lead

Page 2: Transactional Monitoring for Loosely Coupled Service Architectures

Some BackgroundWho I am and what I do• Daniel Khan• @dkhan• [email protected]• Technology lead @Dynatrace• Performance Monitoring

Page 3: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

The ConsumersView

Page 4: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

2000

Page 5: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

2005

Page 6: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

2016

Page 7: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

The new world of Microservices

Teams choose their technologies freely Independent deployment Elastic scaling Service brokers Circuit breakers Unknown or obscure dependencies Randomly interwoven third party dependencies The monoliths are still somewhere

Page 8: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

The website is

slow!

Page 9: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Find the Faulty Part

Page 10: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 11: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Find out before the User does

Page 12: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

So we have to Monitor

Page 13: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Follow each Transaction

Page 14: Transactional Monitoring for Loosely Coupled Service Architectures

Complete Transaction CoverageBrowser / Native Mobile Java/

.NET

PerformanceWarehouse

PurePathCollector

DynatraceServer

DynatraceClient

SessionsStore

ExportedSession

OfflineSession Analysis

Web Server/ PHP

C++, VB, ADK

CICS

Mainframez/OS

MQ/ESB

Database

Page 15: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 16: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 17: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

2016

Page 18: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

3 Metrics per Service

5 Metrics per Host

5 Metrics per Runtime

40 Services = 120 Metrics

20 Hosts = 100 Metrics

40 Runtimes = 200 Metrics

420 Metrics

Page 19: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

We cannot watch 400+ metrics So we need to find ways to automate finding anomalies

Page 20: Transactional Monitoring for Loosely Coupled Service Architectures
Page 21: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Response Times

Error Rates

Load

Anomaly Detection

Page 22: Transactional Monitoring for Loosely Coupled Service Architectures

Historic

Data

“Normal”

Model

New Data

Hypothesis

Likeliness

Judgement

update

calculate derive

testproduces

Anomaly?

defines

Anomaly Detection Workflow

Page 23: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Distinguish Impact from Cause

Page 24: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slowdown

Page 25: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slowdown

Dependent services slow down

Page 26: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slow down

Dependent service slow down

Users are affected

Page 27: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slow down

Dependent service slow down

Users are affected

Analyze Dependencies

Page 28: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slow down

Dependent service slow down

Users are affected

Analyze Dependencies

Exclude non-relevant services

Page 29: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slow down

Dependent service slow down

Users are affected

Analyze Dependencies

Exclude non-relevant services

Follow causality chain

Page 30: Transactional Monitoring for Loosely Coupled Service Architectures

Automated Analysis of ProblemsService slow down

Dependent service slow down

Users are affected

Analyze Dependencies

Exclude non-relevant services

Follow causality chain

Page 31: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Productized

Page 32: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 33: Transactional Monitoring for Loosely Coupled Service Architectures
Page 34: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 35: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Page 37: Transactional Monitoring for Loosely Coupled Service Architectures

@dkhan

Thank You! | Daniel Khan | @dkhan | [email protected]