Grainger's Our Rookie Year with Zenoss is presented by Mark Cochrane (Manager, Enterprise Systems Management) and Dan Ozanich (Infrastructure Software Admin). Access the full presentation recordings for GalaxZ17 here: http://ow.ly/WyBu30cakk0

1. Monitoring Roadmap
Mark Cochrane
Manager Enterprise Monitoring
Grainger
GalaxZ Conference
April 11th, 2017
#GALAXZ17
OUR
ROOKIE
YEAR WITH
ZENOSS

2. Grainger – “Get it. Got it. Good.”
Grainger helps professionals
save time and money in
keeping their operations
running and their people safe

3. Grainger – “Get it. Got it. Good.”
• Grainger is a leading B2B
distributor of products used to
maintain, repair, and operate
facilities (MRO)
• Founded in 1927, a global Fortune
500 company
• Approximately 3 million active
customers (business and
institutions)
• 1.5 million products stocked
• 4800+ suppliers
• 11th largest e-retailer in the North
America
• $10.1 billion in sales in 2015

4. 2016: The first steps…
• POC with Zenoss 2015
• Purchased in April 2016
• Began build out June 2016
• Parallel testing with GCC 3/31/16
• Go Live 5/1/17

5. Infrastructure
Discovery
Ease and simplicity compared to Big 4
 Individual
 Network
 Integration with Service Now CMDB
Modeling
 Out of the Box
 Need to know device type

6. Infrastructure
Challenges
 Environment Complexity
 Security
 Known Inventory/CMDB

7. Applications - Services - Integrations
Steps for application monitoring
 1. Device connection and configure core
components (IP Services/Processes, etc)
 2. Setup triggers and notifications
 3. Create service impact views with components
 4. Create service impact rules and events

8. Applications - Services - Integrations
Zenoss used as a service tool for applications
 Giving access to make changes to thresholds, groupings,
what is monitored, and other items
 Ease of use within Zenoss allows for this access
 Discovery of components also contributes to the ease of
use
 Limitations to granting/limiting access to users within
Zenoss
 Certain configuration items will be kept with monitoring
team. (ex. URL and process monitoring)

9. Applications - Services - Integrations
Integration Successes
 Service Now
incident creation
 Slack
 HP OML forwarding
of events into
Zenoss
 OEM
Challenges
 WinRM connection
with non-admin
account
 Sizing Zenoss deploy
 Event storms

13. The road ahead…
• Parallel Testing with GCC
• Go Live tentatively 5/1/2017
• Addition of Voip devices
• Additional Branches
• Upgrade Analytics
• Build out Reporting (Veeam)
• Automation
• Stability and capacity challenges
• Application Team acceptance
• Process improvements with integration
to SNOW
• CMBD seeding/updates
• Integration with Grainger Openstack
private cloud
• DCIM

14. Monitoring Maturity Model
LEVEL
1
LEVEL
1 2 3 4 5
LEVEL
LEVEL
LEVEL
LEVEL
• Scalable, future-
proof monitoring
platform
• Tool consolidation
• Root Cause Analysis
• Medium MTTR
• Alerts are
meaningful &
actionable
• Operational data
visualization for the
business
• SLAs measured and
communicated
• IT teams creating
views & dashboards
with meaningful data
• Full integration with
CMDB/ServiceNow/
Slack/Mir3/Openstack
• Capacity forecasting
is established
• Fully automated
monitoring visibility
on premise and
Cloud
• Low MTTR
• 99% visibility
• Self healing systems
• High quality alerts in
the GCC
• Decrease in OPEX
and CAPEX
• Establish a
monitoring roadmap
limiting tools
• Investment in
monitoring tools and
teams
• Establish operational
procedures within
the GCC
• Teams are “doing
their own thing”
• Tool overlap and
creep
• Limited visibility
• Long MTTR
• Minimal services
being monitored
• Excessive emails
and false alerts
AD-HOC
MONITORING
BASIC
AVAILABILITY
STANDARDIZATION
& CONSOLIDATION
ADVANCED
VISIBILITY
OPTIMIZED
SERVICE
DELIVERY

15. Questions, comments, thoughts….