5. 5
Supported
Protocols
In
Splunk
App
for
Stream
v6.0
• UDP
• TCP
• HTTP
• IMAP
• MySQL
(login/
cmd/query)
• Oracle(TNS)
• PostgresSQL
• Sybase/SQL
Server
(TDS)
• FTP
• SMB
• NFS
• POP3
• SMTP
• LDAP/AD
• SIP
• DNS
• DNCP
• Radius
Linux
32-‐bit/64-‐bit
and
Mac
OSX
64-‐Bit
Linux
only
6. Why
Wire
Data?
6
• Wire
data
compliments
Log
data
• Wire
Data
can
contain
IT
and
business
informaIon
not
found
in
Log
data
and
vice
versa
• Wire
Data
can
be
passively
gathered
without
any
impact
to
producIon
workloads
without
tagging,
embedded
code,
or
addiIonal
agents
• Wire
Data
does
not
require
semanIc
logging
by
customer
or
byte-‐code
instrumentaIon
• Wire
Data
can
be
gathered
across
many
protocols
(SSH,
FTP,
SMTP,
IMAP/MAPI,
TDS,
MQTT,
etc.)
• Can
be
A
LOT
of
data!
A"ribute
Log
Data
Network
Data
WIRE
DATA
/
LOG
DATA
FOR
HTTP
WEB
TRAFFIC
7. What
is
available
from
the
Wire?
7
Performance
Metrics
Round
Trip
Time
Client
Request
Time
Server
Reply
Time
Server
Send
Time
Total
Time
Taken
Base
HTML
Load
Time
Page
Content
Load
Time
Total
Page
Load
Time
ApplicaGon
Data
POST
Content
AJAX
Data
SecIon
Sub-‐SecIon
Page
Title
Session
Cookie
Proxied
IP
Address
Error
Message
Business
Data
Product
ID
Customer
ID
Shopping
Cart
ID
Cart
Items
Cart
Values
Discounts
Order
ID
Abandoned?
8. Example
Customer
Use
Case
" Customer
FrustraIon
– DBA’s
refuse
to
provide
visibility
to
Log
events
(i.e.
SQL
Queries)
or
DB
performance
! No
Splunk
Forwarder
on
SQL
hosts
– Need
bemer
visibility
into
HTTP
traffic
for
security
purposes
! Logs
from
Web
Servers
contains
some
but
not
all
data
" SoluIon
– Use
App
for
Stream
to
grab
data
off
the
wire
!
Out
of
Band
collecIon
to
get
SQL
performance
using
Stream
from
the
ApplicaIon
side
! “Use
Splunk
as
an
IDS
to
see
strange
things
on
the
wire”
8
9. TURN
WIRE
DATA
INTO
OPERATIONAL
INTELLIGENCE
CLOUD ON-PREMISES
Splunk App for Stream (FREE)
11. What
is
“Splunk
Stream
Add-‐on?”
" Technology
Add-‐on
or
TA
(Splunk_TA_stream)
" Provides
a
new
Data
Input
called
“Wire
Data”
– passively
captures
traffic
using
a
modular
input
– C++
executable
called
“Stream
Forwarder”
(streamfwd)
" Captures
applicaIon
layer
(level
7)
amributes
for:
– UDP,
TCP,
DHCP,
DNS,
FTP,
HTTP,
IMAP,
LDAP,
MySQL,
NFS,
POP3,
PostgreSQL,
SIP,
SMB,
SMTP,
TDS,
TNS,
and
more
" AutomaIcally
decrypts
SSL/TLS
traffic
using
RSA
keys
11
12. Stream
Forwarder
Architecture
12
Protocol
Decoder
Events
DecrypGon
Request/
Response
Network
Interface
(eth1)
Standard
Out
(To
Splunk
Forwarder)
Packets
Flows
Request/
Response
Request/
Response
Protocol
Decoder
Events
DecrypGon
Standard
Out
(To
Splunk
Forwarder)
Protocol
Decoder
Events
DecrypGon
Standard
Out
(To
Splunk
Forwarder)
Network
Interface
(ethN)
Packets
…
Threads
13. Relevant
Moving
Parts
" All
Plasorm
(Linux
x86,
Linux
x64,
Darwin)
binaries
shipped
with
TA
" inputs.conf
– [streamfwd://streamfwd]
splunk_stream_app_locaIon
=
hmp://localhost:8000/en-‐us/
custom/splunk_app_stream/
disabled
=
0
" Config
held
in
memory
on
Streamfwd
" Splunk_TA_stream/default/streamfwd.xml
– Which
interfaces
to
listen
on
13
15. What
is
“Splunk
App
for
Stream?”
" Includes
a
new
Splunk
Stream
Add-‐on
(TA)
– AutomaIcally
installs
the
TA
locally
(disabled)
– Makes
it
easy
to
deploy
TA
using
Deployment
Server
" Manages
configuraIon
for
all
Stream
TA’s
" Provides
REST
API
for
configuraIon
" Includes
New
Dashboards
" Supported
Plasorms:
Linux
32/64bit
&
Mac
OSX
64bit
15
17. AggregaIon
“Many
to
One”
17
Key
amributes
make
aggregaIon
buckets
unique
Sum
amributes
summarize
numeric
metrics
I
want
one
event
every
60
secs
Capture
Data
for
Specific
Events
• Buckets
always
include
a
“count”
amribute
for
#
of
events
it
represents
• Buckets
are
flushed
on
a
configurable
interval
of
Ime
18. Stream
Filters
" Filters
allow
you
to
only
capture
data
for
specific
events
" Example:
HTTP
with
status=404
(File
Not
Found)
18
19. Simple
Deployment
Supports
Fast
Time
to
Value
19
Respond
quickly
to
incidents
by
rapidly
deploying
data
collecIon
directly
from
the
interface
Scale-‐out
deployment
across
enterprise
networks
with
centralized
configuraIon
and
management
21. Architecture
Deployment
OpIon
1
Dedicated
Server
21
End
Users
SPAN
or
TAP
Firewall
Splunk
Indexers
Search
head
Linux
Forwarder
Splunk_TA_Stream
Servers
Internet
22. Architecture
Deployment
OpIon
2
Run
on
Servers
22
End
Users
Firewall
Splunk
Indexers
Search
head
Physical
or
Virtual
Servers
Universal
Forwarder
Splunk_TA_stream
Internet
Physical
Datacenter,
Public
or
Private
Cloud
23. Summary
23
Enhanced
OperaGonal
Intelligence
Efficient,
Cloud-‐ready
Wire
Data
CollecGon
Simple
Deployment
Supports
Fast
Time
to
Value
Explore,
analyze
and
visualize
real-‐Ime
wire
data
for
OperaIonal
Intelligence
Instantly
access
wire
data
across
infrastructures
with
a
simple
so}ware
soluIon;
manage
wire
data
volumes
with
fine-‐grained
filtering
Enable
rapid
deployment
and
reduced
complexity
with
interface-‐driven
install
and
configuraIon
Splunk
Stream
Delivers
Wire
Data
AnalyIcs