SplunkLive! London 2015 - DevOps Breakout

SplunkLive! London 2015 - DevOps Breakout

• 1.
  Copyright  ©  2015  Splunk  Inc.   Splunk  for  DevOps   Stela  Udovicic   Sr  Product  Marke2ng  Manager,   Splunk  
• 2.
  Disclaimer During  the  course  of  this  presenta?on,  we  may  make  forward  looking  statements  regarding  future  events  or  the   expected  performance  of  the  company.  We  cau?on  you  that  such  statements  reflect  our  current  expecta?ons  and   es?mates  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  presenta?on  are  being  made   as  of  the  ?me  and  date  of  its  live  presenta?on.  If  reviewed  aNer  its  live  presenta?on,  this  presenta?on  may  not   contain  current  or  accurate  informa?on.  We  do  not  assume  any  obliga?on  to  update  any  forward  looking  statements   we  may  make.  In  addi?on,  any  informa?on  about  our  roadmap  outlines  our  general  product  direc?on  and  is  subject   to  change  at  any  ?me  without  no?ce.  It  is  for  informa?onal  purposes  only  and  shall  not,  be  incorporated  into  any   contract  or  other  commitment.  Splunk  undertakes  no  obliga?on  either  to  develop  the  features  or  func?onality   described  or  to  include  any  such  feature  or  func?onality  in  a  future  release.  
• 3.
  Build   Unit  Tes?ng   Code   Check-­‐in   Integra?on   Tes?ng   Deploy   Staging   3   Applica2on  Development  Challenges  
• 4.
  Build   Unit  Tes?ng   Code   Check-­‐in   Integra?on   Tes?ng   Deploy   Staging   Lack  of  visibility  across  the  product   development  lifecycle   Pressure  to  increase  velocity  and  agility   with  DevOps   Limited  insights  into  behavior  and   performance  from  applica?on  logs   4   Applica2on  Development  Challenges  
• 6.
  Splunk  Provides  Visibility   6   ROOT  CAUSE   AND  ISSUE   RESOLUTION   PROACTIVE   MONITORING     AND  REAL-­‐TIME   ALERTING   DELIVER  BETTER   QUALITY  CODE   FASTER   CLOUD  APP  AND   INFRASTRUCTURE   MONITORING   MOBILE  APP   TROUBLESHOOTING   USER  &  USAGE   ANALYTICS  
• 7.
  •  Write  log  data  to  local  file   •  Ins?tute  a  log  rota?on  policy   •  Begin  each  event  with  a  ?mestamp  including  ?me  zone  (ISO  8601  Format)   •  Generate  a  unique  iden?fier  that  will  be  assigned  to  all  related  events   •  Use  key-­‐value  pairs  to  describe  the  proper?es  of  each  event   •  Write  events  with  the  appropriate  log  level  and  source   •  Standardize  your  field  names  across  the  applica?on   •  Avoid  excessively  long  events   •  Avoid  spamming  the  log       Follow  Logging  Best  Prac2ces   Write events in a human readable format 7  
• 8.
  Deliver  Quality  Code  Faster   8 Cleaner   Logs   Beger   Coding   Prac?ce   Improved   Tes?ng   Fewer  and   Shorter   Outages   Stable   Produc?on   Performance   Improved   Quality  of   Releases   Splunk  enables  developers  to   gain  access  to  log  files  across  all   environments,  which  led  to   improved  logging  of  key  data     and  beger  coding  prac?ces     Real-­‐?me  access  to  data  during   test  cycles  and  improved  quality   of  releases     Splunk  helps  teams  improve   stability  and  performance  of  all     environments  (Dev,  QA,   Produc?on)   Faster   Resolu?on  of   Project  Issues    
• 9.
  Get  Data  From  Anywhere   9
• 10.
  Collect  Data  Across  Lifecycle  Tools   10 CI  /  Build   Servers   Project  and  Issue   Tracking   Code   Repository   Automa?on   Tools   Dev/Test/Staging   Servers  
• 11.
  CI  /  Build   Server   Code   Review   Task   Tracking   Search  and  Explore  Data   11 Which  code  has  already  been  reviewed  for  this  release/sprint?  Who  has  completed  the   most  code  reviews?  What  code  has  NOT  been  reviewed?     Who  is  changing  files?  What  kinds  of  files  are  being  changed?  What  branches  are  most   ac?ve?  What  types  of  ac?vi?es  are  occurring  for  a  branch?   Version   Control   How  many  builds  completed  today/this  week/this  month?  Which  check-­‐in  kicked  off  this   build?  Which  tests  ran  against  this  failed  build?   Which  tasks  are  assigned  to  which  developers?  What  progress  is  being  made  to  complete   assigned  tasks?  What  tasks  remain  for  this  release/sprint?    
• 12.
  Search  -­‐>  Visualize  -­‐>  Monitor  -­‐>  Repeat   12
• 13.
  Copyright  ©  2015  Splunk  Inc.   Demo
• 14.
  Key  Benefits   14             Reduced  Time   to  Market   Shrink  the  ?me  it   takes  to  get  code   through  dev/test  to   market  through   faster  issue   iden?fica?on  and   resolu?on     Increased   Agility   With  real-­‐?me   visibility  into   processes  like  code   check-­‐ins,  builds  and   tests  to  support   DevOps  prac?ces  like   con?nuous   integra?on     “Our  devs  are  now  able  to   find  and  fix  issues  5  to  10     7mes  faster.”   “We  can  monitor  all  the   automa7on  and  handoffs  it   takes  to  deploy  5-­‐10  7mes     a  day”   Applica2on   Insights   Instrument  customer   applica?on  logs  to   capture  cri?cal   business  events  and   user  behavior   “My  code  isn’t  ready  un7l   it’s  Splunk-­‐ready”  
• 15.
  Copyright  ©  2015  Splunk  Inc.   Customer Examples
• 16.
  Con2nuous  Integra2on  &  Deployment  with  Splunk   16 “Dump  all  the  logs  into  Splunk,  and  it  starts  looking  like  one  big  system,  instead  of   a  bazillion  teeny  ones  that  hate  each  other.”   Alison  Perkins   Senior  Systems  Engineer   •  Challenges:     –  No  single  place  to  access  and  visualize  machine  data   –  Manual  diagnosing  and  searching  through  data  generated  by  servers  and  applica?ons   –  To  retrieve  informa?on,  sysadmins  have  to  ssh  into  produc?on  machines  before  sending  off  to   developers  to  grep  through  the  logs     •  With  Splunk:   –  Quickly  validate  and  troubleshoot  code  pushes  to  produc?on   –  Ensure  that  new  code  does  not  nega?vely  impact  performance  or  user  experience     –  Reduced  one  applica?on’s  error  rate  by  2  orders  of  magnitude  in  a  mager  of  weeks  
• 17.
  •  Challenges:     –  Teams  struggle  to  recognize  errors  in  new  builds  due  to  infrastructure  complexity     –  Logs  are  siloed,  scagered  across  dozens  of  servers,  without  a  single  view  and  with  no  ability  to   correlate  or  search  other  than  manual  processes   –  Lack  the  ability  to  analyze  trends  and  iden?fy  outliers     •  With  Splunk:     –  Increased  success  rates  of  deployments  –  lower  errors  for  new  builds   –  Detect  issues  prior  to  them  having  an  affect  on  the  produc?on  process   –  Aler?ng  on  thresholds  for  event  log  errors  -­‐  roll-­‐back  problema?c  deployments  or  diagnose  a  build  in   a  subset  of  the  produc?on  environment     Splunk  Enables  DevOps  Agility   17 “It’s  like  we  were  working  without  peripheral  vision  before  and  now  we   have  it.”   Robert  Gonsalves   Web  Opera?ons  
• 18.
  Splunk  for  QA    Improves    Agility  and  Code  Quality   18 “Developers  are  now  able  to  look  for  errors  and  troubleshoot  issues  5  to   10  2mes  faster  by  having  all  their  event  data  centralized  in  Splunk.”   Nate  Smalley   Principal  Engineer   •  Challenges:     –  Difficulty  iden?fying  defects  –  finding  and  fixing  issues  took  days/weeks     –  Developers  struggled  to  ensure  that  insights  can  be  gleaned  from  custom-­‐built  applica?ons  around   user  behavior  and  performance     –  No  automated  alert  system  to  immediately  no?fy  team  about  errors   •  With  Splunk:   –  Provide  full  visibility  into  Sanity  and  Load  tes?ng  in  QA  environments     before  deploying  to  produc?on   –  Assists  in  troubleshoo?ng  if  tests  do  not  contain  the  expected  results     –  New  code  is  not  ready  un?l  the  logs  are  Splunk-­‐friendly  
• 19.
  Copyright  ©  2015  Splunk  Inc.   Wrap-up
• 20.
  •  Splunk  can  be  valuable  for  applica?on  development  and  DevOps   •  Find  and  fix  issues  with  real-­‐?me  search  and  monitoring     •  Splunk  can  correlate  data  from  disparate  tools  across  your   applica?on  lifecycle  to  give  your  real-­‐?me  insights  and  help   reduce  ?me  to  market   •  Many  customers  are  using  Splunk  to  support  DevOps  –  you  can   too!     Summary   20  
• 21.
  Tutorials,  Code  Samples,  Genng  Started,  Downloads   •  hgp://dev.splunk.com/   •  hgps://splunkbase.splunk.com/  (Apps  for  Chef,  GitHub,  Puppet,  etc)   Support   •  hgps://www.splunk.com/page/submit_issue     GitHub   •  hgps://github.com/splunk/   Twiger   •  hgps://twiger.com/splunkdev     Blog   •  hgp://blogs.splunk.com/dev/     Resources   21
• 22.
  22   The  6th  Annual  Splunk  Worldwide  Users’  Conference   •  September  21-­‐24,  2015       •  The  MGM  Grand  Hotel,  Las  Vegas   •  4000  IT  &  Business  Professionals   •  2  Keynote  Sessions     •  3  days  of  technical  content   –  165  sessions   •  3  days  of  Splunk  University   –  Sept  19-­‐21,  2015   –  Get  Splunk  Cer?fied  for  FREE!     –  Get  CPE  credits  for  CISSP,  CAP,  SSCP,  etc.   –  Save  thousands  on  Splunk  educa?on!     •  80  Customer  Speakers   •  80  Splunk  Speakers     •  35  Apps  in  Splunk  Apps  Showcase   •  65  Technology  Partners   •  Ask  The  Experts  and  Security  Experts,   Birds  of  a  Feather,  Chalk  Talks  and  a  new   &  improved  Partner  Pavilion!     •  Register  at  conf.splunk.com      
• 23.
  Thank You