Understanding Microservice Latency for DevOps Teams: An Introduction to New Relic Distributed Tracing

2. 2 Housekeeping Confidential ©2008-17 New Relic, Inc. All rights reserved. Today’s webinar is being recorded. A link to the recording will be emailed to all registrants shortly after. Please be sure to ask any questions via the “Questions Panel”. There will be a brief survey after the webinar for any additional questions or feedback.

7. RDS AWS S3 NoSQL Kafka SQS Managing complexity in modern architectures

9. Understanding a request in a Monolith 9 Original Application Result New Relic Agent

10. Understanding a request through your Microservices 10 Original Application Microservice A Microservice BExternal Service MicroserviceC Result New Relic Agent New Relic Agent New Relic Agent New Relic Agent New Relic Agent

12. ©2008–18 New Relic, Inc. All rights reserved • Up and downstream dependencies linking your applications • Error prone call chains Resolve Issues Faster with Distributed Tracing 12 Troubleshoot Discover Optimize • End to end call chains across your microservice architecture • Errors, no matter where in the call chain they are • Redundant calls to the same service • Individual services in your call chain and immediately see the improvements

14. Query results received REST API call sent Query sent How does distributed tracing REALLY work? Java service DBHttp req received Node.js service Http req receivedTrace Context: - Trace ID: abc123 - Parent ID: 2bbb - Sampled: true End-user request Trace Context: - Trace ID: abc123 - Parent ID: 1aaa - Sampled: true TraceID: abc123, ParentID: 1aaa, Name: /user-info, Id: 2aaa, Type: server, Start-time: 1519617397005, End-time: 1519617397105 TraceID: abc123, ParentID: 2aaa, Name: sql/getuser, Id: 2bbb, Type: database, Start-time: 1519617397006, End-time: 1519617397186 TraceID: abc123, ParentID: 2aaa, Name: get-avatar-url, Id: 2ccc, Type: client, Start-time: 1519617397087, End-time: 1519617397107 TraceID: abc123, ParentID: 2ccc, Name: /avatar-url, Id: 3aaa, Type: server, Start-time: 1519617397089, End-time: 1519617397105 New Relic Agent data sent to New Relic Http req completed REST API response received Http req completed

15. Confidential ©2008–17 New Relic, Inc. All rights reserved New Relic Distributed Tracing Automated end-to-end implementation 11 15 Service 1 Agent Service instrumentation Instrument Propagate Context Service 2 Trace Context Agent Service instrumentation New Relic Trace Data Record Trace Data Ingest Analysis Storage Instrument Visualize Traces

17. ©2008–18 New Relic, Inc. All rights reserved Distributed Tracing Recap Automatic instrumentation Trace dimensionality and findability Depth of detail where you need it Focus on building your business, not tools

18. ©2008–18 New Relic, Inc. All rights reserved We’ve found New Relic’s distributed tracing to be super-easy to integrate...we simply updated our agent, and all of the sudden we had distributed tracing. It was a great experience. 18 Andrew Potter, senior developer at Dealer.com, a Cox Automotive brand

20. New Relic is the Catalyst 20Confidential ©2008–17 New Relic, Inc. All rights reserved. NEWR NYSE – 2014 17k+ Customers 2B+ Scale: Events & Metrics Per Minute 15,000+ Disruptors2000+ Global Enterprises Delivering the real-time insights that software-driven businesses need to innovate faster. 300+ Microservices

21. ©2008–18 New Relic, Inc. All rights reserved Move fast with confidence Find and fix inevitable issues fast Find places to optimize your code to delight your customers Release frequently so you can innovate quickly, with confidence