FutureStack16 NYC - Aug 9, 2016 Jim Stoneham, VP Product, New Relic

1. Increasing MTBLS
with New Relic
Jim Stoneham
VP Product
@jimstoneham

2. Safe Harbor
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 we make 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.

4. Meatballs Team

5. Focused on monitoring change
Dynamic
environments
(AWS / cloud,
Docker / containers)
Agile / rapid
deployment
pipelines
DevOps cultures
with many hands
on resources
Increasing
pace of
vulnerabilities /
exploits

6. "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."

7. Increasing MTBLS
 Incident triage and resolution > MTTD and MTTR reduction
 Change + health monitoring > Avoid downtime/incidents
 Zero-day vulnerabilities/search needs > Ops team efficiency
 Resource Optimization (esp on AWS) > Save money
 100% visibility of all team actions > Support your DevOps culture

8. Health metrics + config changes
5 sec metrics for
host CPU, memory,
disk, network,
processes
Changes made to
packages, files,
kernel, processes,
user sessions
Current live state of
all resources

9. 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

10. Incident triage
and resolution

11. Incident triage
and resolution

12. Change
and health
monitoring

13. Change
and health
monitoring

14. Zero day /
search

15. Resource
optimization

16. 100% visibility
of team
actions

17. Built on top of NRDB
All metric and event data
is available in NRDB to allow for
more detailed Insights
exploration and dashboarding
Integrates with New Relic APM
for full visibility
across the stack

18. Under the covers
Matt Wagner

19. Elasticsearch NRDB
INVENTORY
INFRASTRUCTURE
EVENTS
METRICS
SAMPLES
 Source Plugin
packages / rpm
 Item Path (ID)
cassandra
 State
version = 2.0
 Time Range
 Inventory Changes
cassandra went
from 1.8 to 2.0
 Agent Events
mydb.example.com
went offline
 Change
Management Events
puppet run failed
 System Sample
overall CPU / memory / IO
 Process Sample
resource usage per process
+ Docker info where relevant
 Storage Sample
capacity and I/O per device
 Network Sample
I/O per device
Common Metadata
Hostname
Agent Version
AWS Region
EC2 Instance Type
Tags (role, environment)
Custom Attributes
Hostname
Agent Version
AWS Region
EC2 Instance Type
Tags (role, environment)
Custom Attributes
Hostname
Agent Version
AWS Region
EC2 Instance Type
Tags (role, environment)
Custom Attributes
= =

20. Inventory
System
Inventory
(Elasticsearch) NRDB
1. Agent sends deltas
2. Current state is stored
and indexed
3. Old state is "retired"
but still searchable
Agent
Ingest API
UI
Infrastructure Events
Inventory Changes
Host Inventory
Installed Packages
Users Logged In
OS Configuration
4. For each change, we create an
"infrastructure event“
This produces the event feed
1
43
Inventory from agents
2

21. Inventory from external integrations (AWS)
Host Inventory
Installed Packages
Users Logged In
OS Configuration
Agent
Ingest API
Inventory
System
UI
Infrastructure Events
Inventory Changes
Host Inventory
Installed Packages
Users Logged In
OS Configuration
AWS
Integration
State from external services uses
the same inventory pipeline
Inventory
(Elasticsearch) NRDB

22. Inventory
(Elasticsearch)
NRDB
1. Agent reports metrics
2. Metrics are decorated
w/metadata from inventory
3. Events are published to NRDB
Common Metadata
OS/Version
Hostname
AWS Region, Tags
Agent
Ingest API
UI
Metrics
General System
Per Process
Per Storage Device
Per Network Interface
Metrics
Processor
1
2 3
Metrics and other events

23. Infra-agent
Go-based
cross-platform
executable
(most Linux
flavors + Windows)
HTTPS / TLS+
server-side
cert checking
Common secrets
sanitized:
keys, passwords,
secrets, tokens, etc.
Runs as root with
light footprint
(CPU / Memory / Storage
/ Net)
Coexists
with Servers,
Opsmatic, and NR
language agents
Uses standard
NR agent key

24. Sign up for beta
go to www.newrelic.com/infrastructure
to request an invite

25. We’d love to talk with you!
Please come see a demo

26. Thank You!