This document discusses how Herbalife, a company that produces health and wellness products, uses Splunk to monitor their global ecommerce website and applications. It describes how Splunk has improved their operational visibility and issue resolution by enabling logging of web, SQL, application, and development data across their four data centers. Splunk has helped them scale from 10GB to 50GB of data in six months, improve mean time to resolution from days to minutes, and support over 250 users accessing logs and metrics.

1. Copyright © 2016 Splunk Inc.

2. 2
Randy A. Miller
Vice President, Development
and Quality - Member
Technology and Strategy

3. 3
Sonification?
Sound of Herbalife’s Ecommerce

4. 4
My Company Overview
• Heath and Wellbeing Products
• My Team designs, develops and runs Herbalife’s global website
and mobile applications.
• 4 Datacenters, in 4 continents, 400+ servers serving 98 countries.

5. 5
My Background and Role
• Development background.
• Now lead dev, qa and ops.
• Favorite Splunk shirt – “Let my people know”.

6. 6
How We Got Started
• Started with 10GB Splunk Cloud.
• Got value in the first day.
• Increased our operational IQ tenfold.
• Improved visibility and trust between teams.

7. 7
Before Splunk
• Manual initiation of log capture.
• Days to get logs, limited access by few team members.
• Often RCAs would be inconclusive due to effort and time.

8. 8
New Process Needed
• Limited performance metrics for predictive sizing
• Error resolution was a time-consuming, manual process.
• Hard to correlate events across devices and server
• No historical data

9. 9
Finding Value With Splunk
• Went from 10-50GB in 6 Months
• Everyone can now see what before only Ops could see. This is
HUGE!
• Major architecture upgrades go smooth and fast with Splunk.
• Frequent daily releases, with low risk now.

10. 10
Production Visibility=Trust
• Went from 4 architecture/operations guru’s to 250+ now
• Now with more authorized users we’ve slashed MTTR from
days or weeks to a mere minute
• Can backcheck logs for customer activity to verify claim
legitimacy
• Capturing web, SQL, app and Dev ALM logs.

11. 11
Slow Pages?

12. 12
What’s on the Load Balancer?

13. 13
Some Ways We Use Splunk
• Now examining how different apps, deployments and versions
can influence various real-time metrics and quality
characteristics
• Instrumented toolsets to journal data to the Splunk platform
to show influence of infrastructure and application changes on
behavior and production

14. 14
Which product has the least number of Errors?

15. 15
How Many Reports, How Big, What Type?

16. 16
Did that deployment make things better?

17. 17
Growing With Splunk
• We’ve created a collaborative community of Splunk experts
spanning multiple departments
• Can manage millions of data points, understand server
performance and monitor applications in a matter of moments,
rather than weeks or months

18. 18
Top Takeaways
• Expose as many people as possible to the Splunk interface
• You’ll discover a lot of amazing things that you didn’t realize were
happening.
• I love Splunk because it has the greatest coverage across many
different technologies, platforms and appliances
• It also has a very mature ecosystem and community

19. 19
Next Steps…
• Now to move into machine learning for more automated
anomaly detection and predictive infrastructure sizing
• Dev Ops - Real-time view of product/dev/qa/release events and
trends

20. 20
Get a Good Night’s Sleep…
“Think about the relevant questions you have and think
about what data you can capture. Don't worry about the
scale and the volume of the data. Splunk is great at
sifting through all that for you”
- Randy A. Miller

21. Thank You