Using New Relic (APM)Knowing your app!

Ollie Brennan@BrOllie

About meSenior Software Engineer @ THE ICONICZCE CertifiedOn Twitter @BrOllie

About me

I have an awesome cat too!

Senior Software Engineer @ THE ICONICZCE CertifiedOn Twitter @BrOllie

Your Dashboard

Keep them visible & relevant

A Story

A Story

Uh-oh!

Errors

Keep your error rate low. It’s the only way you will know if bugs are introduced

The Error

Note: adding custom attributes will help debug later on

Transaction Breakdown

- Drill into your data to find bottlenecks- Know your slow processes & causes

How do we know?

• New Relic dashboards• HipChat/Slack notifications• New Relic mobile app notifications• Emails• Text messages• Dashboards (we have three)

How do we know?

How bad was it?

- Very high response times for some users- Due to our infrastructure, minimal users affected

- Although those who wanted to checkout would have been - New Relic meant we responded quickly and fixed fast

Note: second peak was mostly unrelated.

Hidden Gems

Key Transactions

Track your business key metrics- Trigger alarms on errors in key metrics- Trigger alarms on drop in apdex (SLOW responses)

What to track?- Payments- High volume transactions- Items of most business value

External Services

Track the bottlenecks that you cannot control- Where possible put into queues

1/2

External Services

Track the bottlenecks that you cannot control- Where possible put into queues

My guess: less traffic means more cache misses

2/2

QUESTIONS?