Disclaimer
2
During
the
course
of
this
[email protected],
we
may
make
forward
looking
statements
regarding
future
events
or
the
expected
performance
of
the
company.
We
[email protected]
you
that
such
statements
reflect
our
current
[email protected]
and
[email protected]
based
on
factors
currently
known
to
us
and
that
actual
events
or
results
could
differ
materially.
For
important
factors
that
may
cause
actual
results
to
differ
from
those
contained
in
our
forward-‐looking
statements,
please
review
our
filings
with
the
SEC.
The
forward-‐ looking
statements
made
in
the
this
[email protected]
are
being
made
as
of
the
@me
and
date
of
its
live
[email protected]
If
reviewed
aPer
its
live
[email protected],
this
[email protected]
may
not
contain
current
or
accurate
[email protected]
We
do
not
assume
any
[email protected]
to
update
any
forward
looking
statements
we
may
make.
Agenda
!
Know
who
you
are
!
Make
things
surprisingly
easy
!
Gather
endorsements
!
Be
helpful
in
many
mediums
!
Promote
your
community
!
Create
champions
!
When
all
else
fails,
hold
a
contest
2014
we
believe…
14
• A
minimal
number
of
associates
need
to
directly
touch
nodes
(approaching
zero)
• These
tools
maUer
–
improve
the
lives
of
our
users
• Tools
should
be
hardened
-‐
so
that
we
can
find
the
root
cause
and
drive
[email protected][email protected]
What
we
need
20
! 1
hour
[email protected] ! Person
in
the
room
with:
– [email protected]
knowledge
of
[email protected]
(which
logs
are
valuable)
– root
access
to
the
node
(so
we
can
bootstrap
Chef)
– knowledge
of
Splunk
and
Chef
(someone
from
my
team)
[email protected]
allies
26
Splunk
has
played
a
vital
role
in
stabilizing
our
Jira
environments.
In
what
would
have
taken
weeks
of
manual
[email protected]
and
analysis
can
be
summarized
in
Splunk
in
maUer
of
minutes.
For
example
we
were
able
to
[email protected]
a
server
was
excessively
calling
our
server,
then
moving
straight
from
that
to
the
URI’s
that
the
server
was
accessing.
We
were
able
to
contact
the
team
that
was
abusing
our
service
and
they
were
able
to
scale
back
their
web
calls
[email protected]
our
slowness
issue.
Without
Splunk
I
feel
that
this
process
would
have
taken
weeks
to
discover,
if
at
all.
This
is
saving
my
team
@me
in
[email protected]@on,
not
to
[email protected]
the
@me
of
all
other
associates
by
resolving
this
slowness
issue
quicker.
Joe
Hostler
System
Engineer,
CWx
Emerging
Technology
Services
Rima
Poddar
38
• Defined
and
explained
evenUype
usage
• Prototyped
first
working
[email protected]
sub-‐ system
hUp://engineering.cerner.com/blog/ managing-‐30000-‐logging-‐events-‐per-‐day-‐with-‐ splunk/
Mike
Hemesath
39
hUp://engineering.cerner.com/blog/ managing-‐30000-‐logging-‐events-‐per-‐day-‐with-‐ splunk/
• Defined
and
explained
evenUype
usage
• First
major
use
of
pivot
tables
• Many
internal
[email protected]
to
other
teams
and
leadership
• Push
for
[email protected]
Summary
!
Know
who
you
are
!
Make
things
surprisingly
easy
!
Gather
endorsements
!
Be
helpful
in
many
mediums
!
Promote
your
community
!
Create
champions
!
When
all
else
fails,
hold
a
contest