Workshop New Relic - juni 2015

Workshop - New Relic

Melvyn SopacuaSenior Support Engineer

@SupportDesk

melvyn.sopacua@supportdesk.nu

NEW RELIC

✓ Performance Monitor

✓ Error Monitor

✓ Uptime Monitor

✓ Alert Dispatcher

Look & Feel

THREE MAIN USES FOR DEVS AND MAINTAINERS

1. Performance optimization track (project based)

2. Elusive bugs and Performance Peaks (incidents)

3. Performance monitoring over time for scalability

TRACK 1: PERFORMANCE OPTIMIZATION

Basic Workflow

● Identify pages that are worth investigating (slow versus

time consumed)

● Set a target page response time (global and for specific

pages)

● Wait for transaction traces to come in and analyse

bottlenecks.

● Buy a new template Fix the code

● Check gain when live or watch the new bottleneck rears

it's ugly head.

PERFORMANCE OPTIMIZATION TRACK

Recursive Loads

Expensive observers

Platform bottlenecks

Too much bling

Shaving the milliseconds

Recursive load

Many Recursive Loads

Many Recursive Loads

Queries

Track 2: Bug or performance bottleneck incident

“What did you do to break it?”

UNABLE TO REPRODUCE THE PROBLEM

“Works for me, so call me back when you see it again”

“Site’s up and running”(and you forgot your /etc/hosts

file)

REPRODUCING THE PROBLEM

✓ 7-day error retention

✓ Graphed

✓ Alertable (based on % of requests)

✓ Traces

Error Rate Screen

Error Trace

Performance Bottleneck

Ready… Aim… Fire!

Track 3: Performance Monitoring

Observe. Respond. Report. Advise.

PERFORMANCE MONITORING TOOLBOX

EVENT ALERTS:

● Application wide ApDex

● Key Transaction ApDex

● Error rates

● Reachability

PERIODICS:

● Weekly Performance Email

● 90 days application wide

● 30 days per transaction

● Historic Performance

Comparison

Ale

rt

Sys

tem

Pro

cess

Reporting the good stuff

Release “Awesome Sauce”

Interested?

DIRECTLY FROM NEW RELIC THROUGH BYTE