32
Increasing MTBLS With New Relic Jim Stoneham - VP Product Mikhail “Pancakes” Panchenko – Dir Engineering

New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Embed Size (px)

Citation preview

Page 1: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Increasing MTBLSWith New Relic

Jim Stoneham - VP ProductMikhail “Pancakes” Panchenko – Dir Engineering

Page 2: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

This document and the information herein (including any information that may be incorporated by reference) is provided for informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc. (“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission.

Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the statement will include words such as “believes,” “anticipates,”, “expects” or words of similar import.

Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof, and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect such forward-looking statements is included in the filings New Relic makes with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at ir.newrelic.com or the SEC’s website at www.sec.gov.

New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New Relic makes no warranties, expressed or implied, in this document or otherwise, with respect to the information provided.

Page 3: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Dynamic full-stack monitoring for modern teams

Page 4: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

4Confidential ©2008-15 New Relic, Inc. All rights reserved.  

Meatballs Team

Page 5: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Focused on monitoring change

Dynamic environments

Agile / rapid deployment pipelines

DevOps cultures with many hands

on resources

Increasing pace of vulnerabilities /

exploits(AWS / cloud, Docker / containers)

Page 6: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

"Gartner believes that more than 80% of all mission-critical IT service outages result from people and process errors and failures, and of

those outages, more than 50% result from a lack of

coordination between change, release and configuration management processes."

Page 7: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

New Relic Infrastructure: key data we collect

Highly granular metrics for host CPU, memory,

disk, network, processes

Changes made to packages, files, kernel,

processes, user sessions

Current live state of all resources

Page 8: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Organized like your infrastructure

Define alerting and dashboards using your

existing metadata

Leverage EC2, Automation (Chef, Puppet, etc.), or

custom tags

Everything scales up and down based on

your tags / metadata

Supports cloud, hybrid datacenter / cloud, +

traditional datacenters

Page 9: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Organized like your infrastructure

Page 10: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Increasing MTBLS: some examples

Incident triage and resolution MTTD and MTTR reduction

Fine-grained change monitoring Avoid downtime/incidents

Global search Ops and InfoSec team efficiency

Resource Optimization Save money (esp on AWS)

Page 11: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

11Confidential ©2008-15 New Relic, Inc. All rights reserved.  

Incident triage and resolution

Page 12: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Incident triage and resolution

Page 13: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Incident triage and resolution

Page 14: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Fine-grained change

monitoring

Page 15: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Global search

Page 16: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

16Confidential ©2008-15 New Relic, Inc. All rights reserved.  

Resource optimizatio

n

Page 17: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Health metrics, plus full live state and change history

Beyond your hosts: AWS Service integrations

Page 18: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

ELB

Page 19: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

CloudFront

Page 20: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

RDS

Page 21: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

21Confidential ©2008-15 New Relic, Inc. All rights reserved.  

Full-stack visibility with New Relic

Are my apps available across all regions?

Are my apps available across all regions?

Are my critical transactions performing well?

Are my critical transactions performing well?

Is my supporting infrastructure available?

Page 22: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Al KemnerPrincipal EngineerPlatform as a ServiceGannett

Page 23: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Gannett / USA Today NetworkGannett Co., Inc. is a next-generation media company committed to strengthening communities across our network.• 500+ digital products• 116 brands• 109 local markets• 114 Million unique visitors• Serves 1.8 Billion Monthly User Minutes• Reaches 45% of the US online internet population (age 18+)

Page 24: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Record traffic numbers across platforms

Web Mobile web

Page 25: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

- HTTP2- Golang- Nodejs- Couchbase- Docker- Kubernetes

Key technologies

Page 26: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Elections real-time monitoring

Page 27: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Heavy use of filters for dynamic infrastructure

Page 28: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

New Relic Infrastructure metrics in Insights

Page 29: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Capabilities ESSENTIALS PROINFRASTRUCTURE KEY FEATURES

Host Health Metrics (CPU, Load, Mem) √ √

Custom Metrics and Events √ √Flexible Alerting √ √

Native AWS EC2 Tag support √ √

Docker Container Monitoring √ √Real-time, searchable inventory √ √

Live-state config-change tracking √ √

Application metrics correlation √ √

Metrics and events available in Insights √ √

Months of data retention 3 13AWS Service Monitoring √

Page 30: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

VM

OS / APP / NR

VM

PHYSICAL SERVERS EXAMPLE (PRO)

2 VMs = 2 Hostst2.micro

m3.medium

AWS EC2 example (Pro)2 Cloud Instances = 2 Hosts

$14.40

$5.80

$1.80

$4.28

Pro: $1.80 - $14.40/host per month Essentials: $.90 - $7.20/host per month

SPECIAL PROMO PRICING

OS / APP / NR

OS / APP / NR

OS / APP / NR

PRICING BASED ON SIZE OF COMPUTE RESOURCES

Page 31: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Confidential ©2008-16 New Relic, Inc. All rights reserved.   31

Integral to the New Relic Digital Intelligence Platform

Page 32: New Relic Infrastructure Intro: Increasing Mean Time Between Loss of Sleep [FutureStack16]

Thank you.To learn more, attend the training session right after this!See the demo at the showcaseand visit newrelic.com/infrastructure